Hi, I've uploaded tarballs of the current libdbi and libdbi-drivers cvs versions. Both will identify themselves as 0.8.3-pre1. I intend to release them as 0.8.3 shortly, unless someone finds showstoppers.
The tarballs are available here: http://libdbi.sourceforge.net/downloads/libdbi-0.8.3-pre1.tar.gz http://libdbi.sourceforge.net/downloads/libdbi-drivers-0.8.3-pre1.tar.gz I'd greatly appreciate (wink, wink) if at least one soul besides me would be kind enough to test this code (and report about the results). My platform is FreeBSD, and I'll run a few tests on a Debian box that I happen to have. Please (wink, wink) try to run tests on other Linux distros, on OS X, MingW, Cygwin, and whatever you may have at your disposal. I've tested the following drivers on my box: firebird, mysql, pgsql, sqlite, sqlite3. Unless I get positive test results from other drivers (wink, wink), these will be the "core drivers", while I'll package the remainder "as is", with no warranties whatsoever that they even compile, let alone do something remotely useful. Please (wink, wink) report any remaining problems right here. A detailed list of changes is appended below. regards, Markus ______ libdbi - database engine client libraries which install exit handlers are not safe to unload on some systems. libdbi now checks the driver capability "safe_dlclose" and leaves those drivers in memory to avoid segfaults. - error handling and reporting was changed once again. The dbi_conn_error_flag() function is now deprecated. Instead, a call of dbi_conn_error() is all it takes to check the error status. This function returns zero if the last operation was successful, < 0 (one of several predefined libdbi error codes) for internal errors, and > 0 for client library errors. To maintain backwards compatibility, dbi_conn_error_flags() reports the same error codes as dbi_conn_error() so older code should not break as long as you checked against the predefined error codes. - deprecated functions will now cause compiler warnings to make you aware of this fact - the documentation was updated accordingly ______________ libdbi-drivers - major overhaul of the firebird driver. The driver is now linked to libfbembed.so instead of libfbclient.so. You can request a local connection (bypassing the server altogether) by using an empty hostname, or a local connection through the server by using "localhost" or the actual computer name as the hostname. The driver should work with Firebird versions 1.5.x and 2.0.x. - changed all driver code to LGPL, and all doc code to GFDL with no invariant sections - made linking drivers against libdbi the default. This behaviour can be switched off by --disable-libdbi, a reversal of the previous default - improved support for MySQL and PostgreSQL connection options - assorted fixes for MinGW compatibility - improved error handling and reporting -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
