Hi, João Henrique Freitas writes: > Is the code stable for product environments?
Probably a matter of definition. I've been using libdbi almost daily for several years now, and I didn't run into any problems so far. The last bug that might have caused data loss was reported and fixed approx. two years ago. If you look at the mailing list archives or the bug trackers, you won't find reports about crashes, data loss, or other bad stories. I assume libdbi is in fairly good shape. > Exists some license issues with others proprietary databases? Can I write > some drivers for others proprietary databases? This was exactly the intention of the original libdbi authors. Make the framework open source, and leave it to the database driver authors what to connect to and how to license that. That is, you can even write drivers for sinister database engines which require to make everything proprietary which is linked against their client library. I don't know if such database engines exist, but libdbi could handle that case. The only license issue that we're currently struggling with are the differing licenses in some of the drivers included in libdbi-drivers. > > Currently, exists some serious issue with the code? > To the best of my knowledge, no. > What are the plans for next releases and new features? > We haven't discussed this for a while. The development model of libdbi is probably best described as "don't fix it unless someone requests new features, or unless new database engine versions require immediate action". Stuff that comes to mind are (speaking of both libdbi and libdbi-drivers): - there are a couple of fixes in cvs which should be made available in an official release - the sqlite3 driver should be rewritten to make use of the new API - firebird version 2 apparently has a new API as well, so the driver should be fixed - fix the licensing differences in libdbi-drivers - we've discussed a "late-binding" libdbi API a while ago. This would be implemented in addition to the strongly typed API that we have now. This new API would allow you to retrieve data as e.g. integer or string, regardless of what the underlying data type is. Data would be transformed transparently by libdbi. I may have forgotten half of what we've been discussing, but these are the things that I recall. Feel free to request further changes if you have some specific usage in mind. Hope this helps Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
