[Chicken-users] Re: status of chickenlib: build process and mysql interface usage sample

[Johannes Groedem]

* gian paolo ciceri <address@hidden>:

> mmmh., chickenlib has something following this schema (dbi/dbd), for
> mysql and oracle - as eggs we've postgresql and sqlite that don't
> follow this approach AFAIK.

I'd be happy to make the PostgreSQL-bindings comply to some standard,
I just wasn't aware of any.  Any suggestions on how to do this?  I
mean, ideally, it should be possible to only change the connect
statement (maybe not even that) and leave the rest of the code as it
is, if you want to change database.  Maybe make the database-functions
TinyCLOS-methods and dispatch on the connection object?  (IIRC, this
is the CLSQL-approach.)

The Python DB-standard just uses packages, FWIW.  I.e. if you want to
change from Oracle to PGSQL, you just import the PGSQL package
instead.  The functions are named the same, and behave (mostly) the
same.

http://clsql.b9.com/
http://www.python.org/peps/pep-0249.html

-- 
Johannes Groedem <OpenPGP: 5055654C>