Hmm, isn't it better to use the github bug tracker? Luaforge is kind of in life support right now. :-)
-- Fabio Mascarenhas On Thu, Oct 7, 2010 at 7:21 PM, Robert Calco <bob.ca...@softcraft-solutions.com> wrote: > I spent some time today reviewing the code after nabbing it at github. > > My priorities are: > > 1. Dealing with known issues that need resolution; > 2. Updating/upgrading existing drivers on all supported platforms (mysql > 5.1, postgres 9, etc.); > 3. Expanding the range of databases supported and adding new features; > 4. Reviewing the API for improvements; > 5. Documenting the API and its road map; > > Please start populating the bug tracker with your issues and feature > requests once again, with confidence that someone is going to pay attention > from now on: > > http://luaforge.net/tracker/?group_id=12 > > :) > > - Bob > > > > On Wed, Oct 6, 2010 at 7:49 PM, Robert Calco > <bob.ca...@softcraft-solutions.com> wrote: >> >> >> On Wed, Oct 6, 2010 at 7:08 PM, Javier Guerra Giraldez >> <jav...@guerrag.com> wrote: >>> >>> On Wed, Oct 6, 2010 at 1:01 PM, Petite Abeille <petite.abei...@gmail.com> >>> wrote: >>> > This is where we diverge, as in my opinion there is no need for any >>> > specialize API to achieve that goal if one could simply query >>> > information_schema directly, across different databases. >>> >>> there's no need for any new layer if you want to access directly, and >>> deal with engine diferences. >>> >>> another layer that presents common info in a common API (list of >>> tables in the DB, list of fields in a table, etc), would be valuable >>> for some applications, and definitely not the job for the lower-lever >>> layer. >> >> Well, we are all vehemently agreeing that the low-level API needs to be >> simple, clean and unencumbered by any preconceptions about its use (other >> than the developer wants fast, unhindered access to the data at the other >> end of the wire). >> >> We disagree about whether optionally to layer anything higher level on top >> beyond that. I am intrigued by various possibilities, but myself not sold >> they all (or even any of them) belong in LuaSQL per se. >> >> First priorities are getting new versions of all the drivers working on >> the latest respective driver APIs, and adding some new drivers, and >> improving the installation/build process (such that it is easy to add new >> drivers and extend existing ones). >> >> - Bob >> >>> >>> -- >>> Javier >>> >>> _______________________________________________ >>> Kepler-Project mailing list >>> Kepler-Project@lists.luaforge.net >>> http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project >>> http://www.keplerproject.org/ >> >> >> >> -- >> Bob Calco >> DBA Softcraft Solutions >> bob.ca...@softcraft-solutions.com >> > > > > -- > 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/ > _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
