According to Michael Dykman <mdyk...@gmail.com> on Fri, 02/24/12 at 11:42: > > That error is coming from neither the MySQL server nor from > DBVisualizer. That is coming from your JDBC driver. Check the > version of that and research the effect of configuration options. > > http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-properties.html
Thanks for the reply. I understood that the error came from the JBDC driver because of the Java class path given in the exception text: com.mysql.jdbc.PacketTooBigException But that isn't the issue. The same DbVisualizer instance works just fine when connecting to the MySQL 5.1.60 server on system A, but fails with the "query too large" exception when trying to connect to the MySQL 5.1.58 server on system B. It strains credulity to think that the same DbVisualizer instance would use two different JBDC drivers when the DbVisualizer connect string begins with "jdbc:mysql://..." in both cases. I found this file in my DbVisualizer installation directory: unix% cat /usr/local/share/dbvis/jdbc/mysql/README MySQL-AB JDBC Driver -------------------- Version: 5.1.16 Files: mysql.jar Reference: http://www.mysql.com DbVis Software AB is a "MySQL Network Certified Partner" and have the right to distribute the Connector/J driver. So what I can't explain is why it works for one and not the other. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template ----------------------------------------->| -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
