BTW, last week I wrote a metacello configuration group
to load GlorpDBX with the native postgres driver. You can evaluate first:
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfGlorpDBX';
load.
and then
(ConfigurationOfGlorpDBX project version: '1.2') load: 'All with PostgreSQL
native
Hi,
I followed your instructions and I've been able to load GLORP
on a Moose Nightly Built image [1].
I run the 844 tests. 839 of them passed (wow),
4 failed and 1 generated an error.
These are the problematic ones:
GlorpManyToManyDBTest>>#testReadNodeAndDeleteChildWithSaveAndContinue
GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary
GlorpDateTest>>#testDate
GlorpObjectMappedToImaginaryTableTest>>#testReadBackEntireExample
GlorpUnitOfWorkTest>>#testRollbackOneToManyAfterAdd
Are these tests failing also on other Pharo images
(i.e., they are known "problems")?
Do you know the impact of these failures?
will GLORP be reliable without them?
Moose developers, would you include
GLORP in the images built by hudson?
I think 839 passing tests are good enough for
the development image.
Ciao,
Alberto
[1]
http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/