On Tue, Oct 5, 2010 at 8:14 AM, Robert Calco <bob.ca...@softcraft-solutions.com> wrote: > Again, this would be optional to keep the core light/simple. :)
+1 for me, an 'ideal' relational DB system would look like this: - a collection of 'drivers' with a common API, but _absolutely_ no SQL tinkering. the user should be guaranteed that any SQL he writes will arrive byte-identical to the SQL engine. this layer is mostly done with LuaSQL. mostly missing are parameterized queries and BLOBs, possibly because most past proposals favored one or another SQL dialect, suggesting it to be emulated for other engines... which is a no-no at this layer. - a 'common SQL' layer, to iron out most syntax differences between SQL dialects. this would for example make a lot easier to use prepared statements and parameterized queries. unfortunately, there are some capability differences that can't be 'fixed' at this layer. for example, recursive queries aren't supported by some engines, and shouldn't be 'emulated' for others. it's possible that this layer would require LPEG to get a robust compiler. maybe it could also present a different API without the compiler, to express - an ORM.... well, not exactly 'O', since i feel that the cleanest Lua code isn't too object oriented. possibly a fluent API to create pseudotables would feel better. there are lots of colors to paint this particular bikeshed. -- Javier _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
