Robert Ladyman writes:
> OK, postgres has a number of python access methods, it might
> be worth splitting the access into a number of methods (we
> use pgdb): just an idea.
What are the pros/cons of each one? IOW, why is it that there
are several dbapi libraries for postgres when one would
suffice?
I had originally set up the dBackend stuff to handle any number
of backend libraries that could just be 'dropped in', but Ed
didn't like that and switched to friendly names such as 'mysql'
instead of 'MySQLdb' - IOW the name of the database instead of
the name of the dbapi library.
Anyway, if pgdb is what you know, and it works and supports all
needed postgres features, then that is what we should use. We
could always make separate postgres db files named
'postgres-pgdb' etc. For now, please just code to pgdb and if
there are problems with that they can be corrected in the
future.
Thanks for taking this on Robert!
--
Paul McNett
http://www.paulmcnett.com
©2004 Paul McNett |
