Cannot run Glorp Tests because "PostgreSQL is not yet supported under VA"

Joachim Tuchel

unread,

Oct 23, 2020, 2:27:15 AM10/23/20

to VA Smalltalk

I am hunting for a bug in our program that is related to Glorp, or most likely, our misuse of it in...

Esteban brought up the idea of loking at some tests, which is a good idea and I wonder why I once again didn't think of it again.

So I found a few tests that use the method in question, and they are green. I tried running all Glorp Tests and got lots of red and yellow tests due to "PostgreSQL is not yet supported under VA".

I think this isn't true any more these days and the tests should be adapted to this.

I guess the problem here is (once again) that VADatabaseAccessor, which throws the error, is part of the base Glorp code and is more or less maintained by someone outside of Instantiations. So what would be needed is some way/meachanism of pushing changes upstream to Glorp. Not sure who (c|sh)ould do something about this....

Any ideas?

Joachim

Bob Brodd

unread,

Oct 26, 2020, 11:40:19 AM10/26/20

to VA Smalltalk

Hi Joachim,

The error message you refer to would occur if you tried to run with a PostgreSQL logon resource prior to VAST 9.2 as that is when PostgreSQL/Glorp support was added to VAST . The message is created in VADatabaseAccessor>>#connectionClassForLogin: . What version of VAST are you testing with?

Bob

Joachim Tuchel

unread,

Oct 28, 2020, 10:34:19 AM10/28/20

to VA Smalltalk

Bob

thanks for answering. This is indeed not a problem of VAST. In a clean 9.2 image with Glorp and GlorpTests loaded, this doesn't happen.

I completely forgot I have this open itom on my to do list of porting my private glorp enhancements to the latest version of Glorp in VAST. When I moved to Vast 9.2, i upgraded everything but Glorp... So I am running on VAST 9.2 but with glorp from 9.1...