So my question is, what else would a driver or db need to provide to enable OpenACS 4.0 support?
Let's see...
- The ability to create and drop tables, views, indexes (including special index types supported by a particular RDBMS), and functions in the native programmatic language.
- Table locking
- rownum or limit/offset
- hierarchical queries (for those RDBMS's that support them)
These come to mind immediately. The ACS traditionally leans heavily on db-specific features, in essence you need to be able to tunnel through the portable ODBC layer to be able to fully support [Open]ACS 4.
I'm unconvinced that going through an ODBC layer doesn't have fairly steep performance implications. It might be an interesting way to prototype support for other RDBMS's, however.
Rewriting query files for a particular RDBMS isn't going to be a huge problem now that we've got the infrastructure mostly in place to do it. For a "real" product supporting a particular RDBMS I think this will be the preferred method.
