The following are some pseudo-random thoughts about putting some spry in LuaSQL's steps:
1. Better make/install procedure. By better I mean detection of available driver libraries should be automatic or at least semiautomatic and all the desired/available drivers should be compiled and installed with one command on either unix or windows, by whatever means necessary. 2. More up-to-date binary drivers for windows. Postgres for example has been particularly neglected for a long time on Windows. Also, v 9.0.1 has recently been released... would be great PR if LuaSQL was among the first language bindings to support it fully. 3. A standard metadata API. Each RDBMS does this differently and it would be nice if developers of, e.g., ORM tools and such did not have to "roll their own" metadata query and manipulation logic. I would probably make these separate clibs to allow developers to load only what they need. The core should remain light/simple. 4. Support additional drivers, e.g., interbase/firebird, db2, etc. 5. (Long term!) A common SQL dialect with some escape sequences for notoriously divergent data types (datetime!). The driver chosen would 'reinterpret' the SQL into the native tongue of its RDBMs for the developer. See: http://download.oracle.com/docs/cd/E13222_01/wls/docs91/jdbc_drivers/sqlescape.html Again, this would be optional to keep the core light/simple. :) Thoughts/suggestions welcome! -- Bob Calco DBA Softcraft Solutions bob.ca...@softcraft-solutions.com
_______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
