On Wed, Mar 29, 2006 at 02:57:15PM +0200, Ivan Horvath wrote:
> i don't know oracle at all
It will be ok to patch only Postgres but in a way that will allow to
extend the patch for other databases. Hence SQLObject needs a consistent
API for schemas.
> i don't know also how do you handle bugs, patches, etc.
First thing to remember is: SQLObject is portable. It must have an API
that works across different Python versions (SQLObject supports Python 2.2
and higher), different DB API drivers (psycopg1 and psycopg2, e.g) and
different database backends - MySQL, Postgres and SQLite are our primary
interest.
We always needs more code and more documentation, but not every patch
could be accepted - we should not lower the quality bar and add quick and
dierty hacks. Every patch for the code should (not "must") be accopanied
with tests and documentation.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
