>> What is the relation between the glorp we have with the VW version?
>
> Outdated, according to Alan Knight in response to a bug I reported.
> The truth is no one knows.

not entirely true.
we know that is outdated :)
Now, our version was ported from (AFAIR) 7.1 and extended to allow our drivers.
Probably next time best path of porting is to make a bridge between VW driver API and ours (but I didn��t estimated the amount of effort).

Ok. In the VW Store, the latest version is:

timestamp: 21 Nov 2013 15:22:32
version: 7.10.1 - 3

I don't really know what it means (the 3rd release of 7.10.1 ?)

��

>
>> Are the two merged often?
>
> As I understand it they kind of forked, because even though GLORP has
> its own multi-dialect layers, it still was "too VW/PGSQL".

> The DBXTalk guys narrowed the gap, but still��

something like that, yeah :P

Ok. Is there a process somewhere on how to convert VW code to Pharo? Just load it would already be cool.

��

> I'd join an community driven "ORM Task Force" for Pharo. IMHO merging
> VW's and Pharo's version won't be an easy quest.
> While debugging GLORP I learnt a few things about its internals, and I
> think other users share the same learning process.
> So I am willing to spend some time on this. :)

Cool !
We might need some people who were involved in the Pharo/Squeak port I guess...

Where is the best place to ask about Glorp by the way?