Ed Leafe writes:
> Developers are not going to need to switch these
> scripts in and out constantly - they'll use the one that
> matches their setup. Therefore I see no need to complicate
> things by making the choice of adapter a dynamic process.
While I liked my dynamic process because it didn't require
editing dBackend.py every time we add another backend adapter,
that isn't what I'm arguing for here. All I want to see is:
dbPostgresSQL-pgdb.py
dbPostgresSQL-x.py
that implement the interfaces to the different db adapters for
postgres, and the appropriate code added to dBackend.py to
allow for BackEndNames of:
PostgresSQL-pgdb
PostgresSQL-x
PostgresSQL
Nothing dynamic here.
> We
> can include the various adapter scripts with Dabo, and if
> someone wants to use one of those, she will simply rename
> that to the common adapter's name, and all will work fine.
Why force them to rename a file (and have to remember to do that
again and again as they upgrade Dabo) instead of giving them an
explicit BackEndName to use? Does it really complicate things
to use the name of the dbapi in the BackEndName?
--
Paul McNett
http://www.paulmcnett.com
©2004 Paul McNett |
