Package: mysql-client-4.1 Version: 4.1.11a-4sarge2 Severity: important We're using an application which runs pretty much 24/7. The DB connection times out due to the wait_timeout setting yet is implicitly recreated during a subsequent mysql_real_query without an error. The new connection does not have the "context" of the old connection. By "context" I mean that settings like "set names utf8;" are lost and the new connection is configured to return and expect latin1 encoding for a utf8 database/server and will therefor return invalid data from the applications point of view and subsequent inserts and updates will corrupt the database data.
IMHO, if the implicit reconnect cannot fully restore the "context" (i.e. the full state) of the connection, then mysql_real_query should simply fail with CR_SERVER_GONE_ERROR or CR_SERVER_LOST as documented: http://dev.mysql.com/doc/refman/4.1/en/mysql-real-query.html Cheers, David Ayers -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages mysql-client-4.1 depends on: ii debianutils 2.8.4 Miscellaneous utilities specific t ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an ii libdbd-mysql-perl 2.9006-1 A Perl5 database interface to the ii libdbi-perl 1.46-6 Perl5 database interface by Tim Bu ii libgcc1 1:3.4.3-13 GCC support library ii libmysqlclient14 4.1.11a-4sarge2 mysql database client library ii libncurses5 5.4-4 Shared libraries for terminal hand ii libreadline4 4.3-11 GNU readline and history libraries ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3 ii mysql-common-4.1 4.1.11a-4sarge2 mysql database common files (e.g. ii perl 5.8.4-8sarge4 Larry Wall's Practical Extraction ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
