I think you would have to give more specific information about your problems. Taking Mysql as example you first have the Mysql module containing Mysql.mysql and Mysql.mysql_result. Then Sql.mysql inherits Mysql.mysql and acts as an interface adapter. Finally the Sql.Sql class creates an internal Sql.mysql object, given a mysql uri, on which it performs its operations.
An idea that I have had is to make things more statically compiled by letting Sql.get_db(string uri) return Sql.Mysql, which inherits Sql.DB (with the contents from Sql.sql) and Mysql.mysql.
/ Martin Nilsson (saturator)
Previous text:
2003-12-19 03:42: Subject: SQL
I started working on an interface to the SQLite database engine (www.sqlite.org) today. The preliminary results are promising, but I'm now at the point where I should decide what direction to take the work. My initial thought is that this should be handled in the same manner as the other database interfaces. I'm not sure how well some of the interface design aspects will fit with the SQLite view of things, though. I was wondering if anyone can give me an idea of what I need to impliment in order to have it accessible through Sql.sql.
Bill
/ Brevbäraren