Hi guys. I am trying to understand how to integrate this in the OpenDBX driver, but I am a little bit lost. First, I don't understand when this #byteArrayToSQLStringConverter is used. What is the bytearray and what is the string? one is the database type and the other one is the inst var of one you your mapping class?
Second, I don't know WHERE to put such conversion in the OpenDBX driver. Why it should be there if #convertSQLStringToByteArray: aString for: aType will continue to exist in Glorp. So it means I should also modify Glorp? How does the EXDI driver of VW work here? Thanks! On Thu, Nov 10, 2011 at 11:15 AM, Henrik Sperre Johansen < [email protected]> wrote: > On 10.11.2011 14:29, Sven Van Caekenberghe wrote: > >> Alan, >> >> On 09 Nov 2011, at 21:20, Alan Knight wrote: >> >> My inclination would be to think that this is something that the >>> database driver ought to be handling rather than having it in Glorp at all. >>> But, given that it's in there, I suppose it's not unreasonable. >>> >> Well, I just extended the previous conversion that was already located >> there. I did not consider whether or not that kind of platform specific >> code was in its right place, architecture wise. >> >> So, will it be integrated somewhere ? If it is only integrated in the >> Pharo/Squeak port that is fine for me too, but it would be frustrating if >> it got lost on the next upstream integration. >> >> I would just love to be able to load the standard release and have it >> working for me (i.e. loading blobs from a recent PostgreSQL). >> >> Thx for the reply, >> >> Sven >> >> I agree with Alan, it should be in the Postgres-specific code of > OpenDBX-driver. > Glorp can't be the only user who wants to read blobs, can it? ;) > > Cheers, > Henry > > -- Mariano http://marianopeck.wordpress.com
