"Dr. Volker Jaenisch" <[EMAIL PROTECTED]> writes: > > | > Trace of an phpmyadmin session directly to a DB-backend bypassing sequoia: > 1656 Connect [EMAIL PROTECTED] on > 1656 Query SELECT VERSION() > 1656 Query SET NAMES utf8 > 1656 Query SET collation_connection = > 'utf8_unicode_ci' > > > After switching the connection to utf8 coding using the "SET NAMES > utf8" sequoia runs into trouble.
> > Conclusions: > * Sequoia is not capable to know the change of the charset since this > * is higly DB-spezific. > * So if the charset is changed during a DB-session sequoia will fail. <http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-charsets.html> The character encoding between client and server is automatically detected upon connection. To override the automatically-detected encoding on the client side, use the "characterEncoding" property in the URL used to connect to the server. WARNING: Do not issue the query 'SET NAMES' with Connector/J, as the driver will not detect that the character set has changed, and will continue to use the character set detected during the initial connection setup. This may not explain the issue you faced, but this is definitely calling for trouble. _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
