On 8/1/05, Yen-Ju Chen <[EMAIL PROTECTED]> wrote: > Since LuceneKit and OgreKit are ready to go, kind of, > I plan to work on a database framework > because I also need one for an application I plan to have. > I think SQLite/SQLDatabase is a good choice. > > SQLite: http://www.hwaci.com/sw/sqlite/ (public domain) > SQLDatabase: http://www.blackholemedia.com/code/ (BSD license) > > Although Berkeley DB XML looks interesting, it has only C++ interface now. > > Any suggestion ? Otherwise, I will port SQLDatabase to Etoile CVS. > It looks quite simple, three source code and two headers only. > Should I keep the namd of SQLDatabase or something like SQLiteKit (or SQLKit)?
Well... I would prefer SQLite over BerkeleyDB. But, why do you want to recreate a new objc framework (or port it) instead of adding a SQLite backend for SQLClient ? Seems to me it would be better to contribute to SQLClient than doing our own framework.. Just in case you don't know about it: "The SQLClient library is designed to provide a simple interface to SQL databases for GNUstep applications. It does not attempt the sort of abstraction provided by the much more sophisticated GDL2 library but rather allows applications to directly execute SQL queries and statements. SQLClient provides for the Objective-C programmer much the same thing that JDBC provides for the Java programmer (though SQLClient is a bit faster, easier to use, and easier to add new database backends for than JDBC)." it's in dev-libs/SQLClient on the gnustep cvs. It currently have backends for PosgretSQL, MySQL and Oracle, although the only backends that seems to be really used/tested are the PostgreSQL ones. Cheers, -- Nicolas Roard "Any sufficiently advanced technology is indistinguishable from magic." -Arthur C. Clarke
