[Seaside] state of the aubergine

[Cees de Groot]

Julian Fitzell <julian@beta4.com> said:
>You can access them but there is no db-independant layer.  We've got 
>around this by abstracting some stuff ourselves but in a case where 
>you're writing something that is going to be re-used for multiple 
>projects and the dbms' involved cannot be predicted, having a generic 
>DBI layer is more than a nicety.
>
So start growing one. 

Last time I did this I just started out with a db-dependent layer
until the request for the first port came. That request hurt a bit, the
subsequent requests hurt a lot less. Certainly I wouldn't take the absence
of a db-independent layer as a reason to let Java enter the picture ;-).

(I'm a bit on my home turf here, having designed and implemented lots of ODBC
and JDBC and even ODBC-to-JDBC-bridging stuff - JDBC and ODBC suck to a large
extent, because Microsoft bloated ODBC beyond recognition and JDBC imitated
that; the original X/Open SAG/CLI spec would probably be a reasonable
starting point for a database independence layer. I'm not sure whether it
floats on the Net somewhere; an old DB/2 programming manual would probably
do, IBM used to stick close to this spec).


-- 
Cees de Groot               http://www.cdegroot.com     <cg@cdegroot.com>
GnuPG 1024D/E0989E8B 0016 F679 F38D 5946 4ECD  1986 F303 937F E098 9E8B