> Why not look at integrating all of the database code from db_wrapper.inc
> into class.DBI structure? We can just add all needed code to the DBD files.
> All of the databases we want to support already have DBD files. We could
> possibly drop some_database_wrapper.inc and db_wrapper.inc files all
> together. Just move that code to the necessary class.DBD::some_database
> files.
Well, I know it would really leave db_wrapper.inc to do much execept actually
make the database connection. However, there may be some things like dealing
with sequences and dates. My main reason for leaving it separate though is
that if there are any changes make to class.DBI we can just plug in the new
class.DBI without having to apply all our changes again. I would prefer to
keep things as compartmentalised as possible.
>
> To make the code and file structure cleaner I agree with the /lib directory
> idea. I'm a sucker for keeping like files grouped into directories.
Okay that is finalised at least.
Regards,
AW
|
