Problems in loading GLORP

Hi,

 By following both Sven's and Mariano's suggestions
(I am referencing see this thread [1]), I am trying to
load GLORP in Pharo. (On a MacOSX 10.6.4, I didn't
tried on other machines).

However, I am not able to complete the loading process.
I tried with both a fresh Pharo image [2] and a Moose development
one. I tried both by using the metacello instructions in SqueakDBX [3],
and by using Sven's script [4].
In any configuration, when it loads GLORP, the loading process
freezes in "Compiling methods".

For example, by using Sven's script, I am able to
run the first three statements, but the fourth freezes
everything:

(1) Scanner allowUnderscoreAsAssignment: true.
(2) Gofer new squeaksource: 'PostgresV2'; package: 'PostgresV2'; load.
(3) Scanner allowUnderscoreAsAssignment: false.
(4) Gofer new squeaksource: 'SqueakDBX'; package: 'Glorp'; load.

Similarly, it freezes following the metacello instructions
in the SqueakDBX site.

Could you please tell me how you are able to load GLORP?

Thank you.

Cheers,
 Alberto


[1] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-June/028664.html
[2] http://www.pharo-project.org/pharo-download/stable
[3] http://squeakdbx.org/Installation
[4] http://www.squeaksource.com/ADayAtTheBeach/GlorpPostgreSQLPharoLoader-SvenVanCaekenberghe.3.mcz

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

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/
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev