Mike Rylander <[EMAIL PROTECTED]> was heard to say: > Continuing this long-dormant thread, I want to thank the libdbi core > team for the help and support in getting basic ISO timezone support > into the code base. It has helped the Evergreen[1] project immensely, > as we wouldn't have a fast and stable database connector without it. >
It is nice to see such a high-profile project use libdbi successfully! > Is it time for 0.8.2? > libdbi has a history of being developed in batch mode. Development usually is dormant as long as no one complains about bugs or missing features. Maybe it is time again for a wake-up call to the hibernating developers to collect all issues which should be addressed in an upcoming new release. From my POV, the following things come to mind (they have been requested previously, but I couldn't find the mails right away as I'm away from my development box): - change the release version numbers to the library interface numbers. The issue has been discussed before (http://sourceforge.net/tracker/index.php?func=detail&aid=1578577&group_id=65979&atid=512948). This change will allow better version checks by the runtime linker and thus will avoid frustrations when using applications built against an incompatible libdbi version. - add a "late binding" interface to libdbi. Currently you have either to know in advance which type a particular query is going to return, or you have to add type checks after each query in order to find out. A "late binding" interface would allow to request e.g. a string or an integer from any type of field, with libdbi performing all required conversions. - the drivers should be overhauled too where necessary. I've fiddled with some experimental code to improve concurrent accesses with sqlite3. Also, we should check at least the MySQL and PostgreSQL drivers with the latest versions of these database engines to work out any compatibility issues. The above issues are just suggestions. If anything else seems worth to be included in the next release, feel free to add your favourites. > > UPDATE: While looking at the code I notices that one of my original > debugging fprintf's managed to hang around. Attached is a patch that > comments out that one line, and does nothing else. It's probably just > as easy for someone to go in and remove all the fprintf lines, > commented out or not, since they're not needed at all, AFAICS. Thanks > again! I've noticed that fprintf message too, but it didn't bother me enough to correct it. I'll do as soon as time permits. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
