I only explained why we choose to avoid the "switch" statement approach,
and suggested that you use the bootstrap/installer multi-db support for your efforts to provide an ODBC/DB2 API within the OpenACS realm.
Talking to multiple RDBMS via the db api would be nice. It doesn't make
sense to talk of an OpenACS installation split across multiple brands of
RDBMS IMO, so this capability is *far* from near the top of any reasonable priority list. After all, you can use ns_db and a pool pointed to the foreign db with no problem, and any such code is going to be in the form of customized additions to your OpenACS installation anyway. Most folks will never have the need for an extended db api, and those that need it have a workaround in the form of the AOLserver ns_db api which is not at all bad, after all...
