http://blog.gmane.org/gmane.comp.db.mysql.java hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.db.mysql.java/5519 <pre>Hello all, MySQL Connector/J 5.1.20, a maintenance release of the production 5.1 branch has been released. Connector/J is the Type-IV pure-Java JDBC driver for MySQL. Version 5.1.20 is suitable for use with many MySQL server versions, including 4.1, 5.0, 5.1, 5.4 and 5.5. It is now available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories. As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc: http://forge.mysql.com/wiki/Contributing MySQL Connector/J 5.1.20 includes the following general bug fixes and improvements also listed in more detail on http://dev.mysql.com/doc/connector-j/en/cj-news-5-1-20.html: - Fix for Bug#64983, 5.1.19 not working with JBoss AS 4.2.3.GA. - Fix for Bug#13960556, java.lang.StringIndexOutOfBoundsException in com.mysql.jdbc.PreparedStatement.formatNanos(int nanos). - Fix for pluggable authentication tests to run on Windows. - Fix for Bug#13897714, NPE in testsuite.regression.StatementRegressionTest.testBug1933() with 5.6.5_m8 server. - Fix for Bug#55962, Savepoint identifier is occasionally considered as floating point numbers. - Fix for Bug#13955027, SET OPTION syntax was removed starting from 5.6.5 server version. - Fix for Bug#13958793, ClassCastException in ConnectionImpl.buildCollationMapping() with 4.1 server. - Fix for Bug#36478, Client prepared statement bugged if word 'limit' included in the query. Enjoy! Tonci </pre> Tonci Grgin 2012-05-02T06:05:11 http://comments.gmane.org/gmane.comp.db.mysql.java/5518 <pre>Hello all, MySQL Connector/J 5.1.19, a maintenance release of the production 5.1 branch has been released. Connector/J is the Type-IV pure-Java JDBC driver for MySQL. Version 5.1.19 is suitable for use with many MySQL server versions, including 4.1, 5.0, 5.1, 5.4 and 5.5. It is now available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories. As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc: http://forge.mysql.com/wiki/Contributing MySQL Connector/J 5.1.19 includes the following general bug fixes and improvements: - Fix for Bug#64621, setMaxRows was not correctly processed during CS PS metadata collection causing entire resultset to be fetched and possibly leading to OOM. - Fix for Bug#63456, MetaData precision is different when using UTF8 or Latin1 tables. The problem was in finding maxBytesPerChar through versioned mapping from Java charset to MySQL charset. That map returns "utf8mb4" instead "utf8" for server versions starting with 5.5.2. CharsetMapping, ConnectionImpl and Field have been reorganized to use static maps INDEX_TO_MYSQL_CHARSET, STATIC_CHARSET_TO_NUM_BYTES_MAP instead. Also dynamic maps ConnectionImpl.indexToCustomMysqlCharset and ConnectionImpl.mysqlCharsetToCustomMblen have been added for custom charsets. - Added support for pluggable authentication via the com.mysql.jdbc.AuthenticationPlugin interface (which extends standard "extension" interface). Examples are in com/mysql/jdbc/authentication and in testsuite.regression.ConnectionRegressionTest. This introduces three new properties: authenticationPlugins defines comma-delimited list of classes that implement com.mysql.jdbc.AuthenticationPlugin and which will be used for authentication unless disabled by "disabledAuthenticationPlugins" property. disabledAuthenticationPlugins defines comma-delimited list of classes implementing com.mysql.jdbc.AuthenticationPlugin or mechanisms, i.e. "mysql_native_password". The authentication plugins or mechanisms listed will not be used for authentication which will fail if it requires one of them. It is an error to disable the default authentication plugin (either the one named by "defaultAuthenticationPlugin" property or the hard-coded one if "defaultAuthenticationPlugin" propery is not set). defaultAuthenticationPlugin defines name of a class implementing com.mysql.jdbc.AuthenticationPlugin which will be used as the default authentication plugin. It is an error to use a class which is not listed in "authenticationPlugins" nor it is one of the built-in plugins. It is an error to set as default a plugin which was disabled with "disabledAuthenticationPlugins" property. It is an error to set this value to null or the empty string (i.e. there must be at least a valid default authentication plugin specified for the connection, meeting all constraints listed above). - Fix for Bug#63526. The problem happens in com.mysql.jdbc.EscapeProcessor#escapeSQL. The function recognizes the string in the create table statement as an escape sequence (line 136+138). The "if" construct beginning in line 182 tries to match a white-space collapsed version of the string to prefixes for valid jdbc-escapes (till line 300). Since no matching escape sequence is found and no "else" clause is defined, neither the token, nor replacement are added to the resulting escaped SQL string. - Fix for Bug#61203, noAccessToProcedureBodies does not work anymore. - Fix for Bug#63811, pointless Socket.bind() when using ephemeral ports and interfaces, which limits scalability on some platforms. - Connection.changeUser() would not check for closed connections, leading to NPEs when this method was called on a closed connection. - Fix for Bug#63284, memory leak with Failover proxied Statement/PreparedStatement with DBCP due to improper implementation of equals(). - Prepared statements would needlessly allocate a 4K buffer for converting streams when no set*Stream() methods had been used. Enjoy! Tonci </pre> Tonci Grgin 2012-04-04T07:22:24 http://comments.gmane.org/gmane.comp.db.mysql.java/5517 <pre>From mysqld Ver 5.0.51a-24+lenny2-log for debian-linux-gnu on i486 To mysqld Ver 5.1.49-3-log for debian-linux-gnu on i486 java.lang.NullPointerException at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:2026) at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:1996) at java.util.Calendar.setTimeInMillis(Calendar.java:1109) at java.util.Calendar.setTime(Calendar.java:1075) at java.text.SimpleDateFormat.format(SimpleDateFormat.java:876) It appears that in mysql-connector-java-5.1.10-bin.jar: com.mysql.jdbc.PreparedStatement line: 4728 this.tsdf.setTimeZone(this.connection.getServerTimezoneTZ()); is null. The combination " useGmtMillisForDatetimes=true&amp;amp;serverTimezone=Europe/Zurich&amp;amp;" in my tomcat's server.xml appears to fix it. Any better hints? Thanks in advance Ralf </pre> gmx 2012-01-15T08:21:25 http://comments.gmane.org/gmane.comp.db.mysql.java/5516 <pre>Hi! Can any body tell me how disable innodb support in mysql embedded connector/MXJ? I know that exist a skip-innodb option for my.cnf file and --skip-innodb as parameter for mysqld, but when i try use it into the server options map this does not disable innodb, i don't know why. I don't need innodb support and it make very slow the mysqld startup. I am using mysql-connector-mxj-gpl-5-0-12.jar and mysql-connector-java-5.1.18-bin.jar Thanks, any help is important to me. </pre> Victor Cifuentes 2012-01-15T05:48:56 http://comments.gmane.org/gmane.comp.db.mysql.java/5514 <pre>Good afternoon, I'm currently trying and configure MySQL in order to have an in-memory database in my unit tests. My environment is: Linux 3.0.0, Java 6 openJDK, MySQL connector 5.0.7 and MXJ 5.0.12. Here's my code: ------------------ String driver = System.getProperty("SQL_DRIVER", "com.mysql.jdbc.Driver"); String defaultUrl = "jdbc:mysql:///test?propertiesTransform=com.mysql.management.jmx.ConnectorMXJPropertiesTransform"; String url = System.getProperty("SQL_URL", defaultUrl); String user = System.getProperty("SQL_USER", "root"); String password = System.getProperty("SQL_PW", ""); Class.forName(driver); Connection conn = DriverManager.getConnection(url, user, password); ------------------ I get an exception at the last line: ------------------ Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:571) at java.util.ArrayList.get(ArrayList.java:349) at com.mysql.management.jmx.ConnectorMXJPropertiesTransform.&lt;init&gt;(ConnectorMXJPropertiesTransform.java:63) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at com.mysql.jdbc.NonRegisteringDriver.parseURL(NonRegisteringDriver.java:639) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:280) at java.sql.DriverManager.getConnection(DriverManager.java:620) at java.sql.DriverManager.getConnection(DriverManager.java:200) at mxj.Start.main(Start.java:25) ------------------ A clue, anyone? Any help will be much appreciated. Regards, Pierre Goupil </pre> Pierre Goupil 2011-12-21T14:24:02 http://comments.gmane.org/gmane.comp.db.mysql.java/5511 <pre>Hello, In my application I have a query which is very hard to rewrite to a preparedstatement for legacy reasons. Is there some method so I can do the right escaping by hand? query = "SELECT * FROM foo WHERE bar = '" + MySQLUtils.escapeString("bla") + "'"; Something like that. Thanks in advance, Ronald.</pre> Ronald Klop (Mailing List 2011-11-04T12:22:19 http://comments.gmane.org/gmane.comp.db.mysql.java/5510 <pre>Hello all, MySQL Connector/J 5.1.18, a maintenance release of the production 5.1 branch has been released. Connector/J is the Type-IV pure-Java JDBC driver for MySQL. Version 5.1.18 is suitable for use with any MySQL version including MySQL-5.1 or MySQL-5.5. It is now available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories. As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.: http://forge.mysql.com/wiki/Contributing MySQL Connector/J 5.1.18 includes the following general bug fixes and improvements: - Fix for Bug#12565726, not putting the space between VALUES() and ON DUPLICATE KEY UPDATE causes C/J a) enter rewriting the query although it has ON UPDATE and b) to generate the wrong query with multiple ON DUPLICATE KEY - Fix for Bug#12784170, "process fork failure" errors while running test suite via ant on Windows. Added new ant flag, com.mysql.jdbc.junit.fork, which controls whether JUnit will fork new processes for testing ("on", default and legacy behavior) or not ("off", required for Windows). - Reverting changes made to ConnectionImpl.java, private boolean characterSetNamesMatches function. - Added function MYSQL_INDEX_TO_MYSQL_CHARSET to retrieve server charset name using index instead of parsing variables to CharsetMapping.java. - Completed fix for Bug#61201/12649557, fixed tests failures. - Fix for Bug#61201/12649557, Can't establish connection when url has sessionVariables and characterEncoding. Fix covers only MySQL server 4.1+ - Fix for Bug#61501 - Calling Statement.cancel() on a statement that isn't currently executing will cause some later-executed query on the same connection to be cancelled unexpectedly. The driver now guards against this condition, but it is an underlying server issue. The MySQL statement "KILL QUERY" (which is what the driver uses to implement Statement.cancel()) is rather non-deterministic, and thus the use of Statement.cancel() should be avoided if possible. - Fix for Bug#61866/12791594 - Calling Statement.getWarnings() after Statement.clearWarnings() has been called, returns the "old" warnings. - Fix for Bug#13036537 - LRUCache was really a least-recently-added cache. - Fix for Bug#13036309, Correcting parameter name in maxPerformance.properties. Enjoy! Tonci </pre> Tonci Grgin 2011-10-04T08:36:03 http://comments.gmane.org/gmane.comp.db.mysql.java/5509 <pre>Hi, I wanted to run java method from trigger. for that i need to write java db procedure.. as mention in http://download.oracle.com/javase/tutorial/jdbc/basics/storedprocedures.html#creating_stored_procedures_java_db but i am getting sql syntax error at 'AS LANGUAGE' please let me know if you have th solution for the same.. my create procedure statement is = "CREATE PROCEDURE log_sal(IN idsal float, IN old_sal float, IN new_sal float) " + //"PARAMETER STYLE JAVA " + "AS "+ "LANGUAGE JAVA " + //"DYNAMIC RESULT SETS 1 " + "EXTERNAL NAME 'com.trigger.DBTrigger.logSal'"; </pre> pravin kalbhor 2011-10-04T05:31:26 http://comments.gmane.org/gmane.comp.db.mysql.java/5508 <pre>To confirm that you would like gcdmj-java&lt; at &gt;m.gmane.org removed from the java mailing list, please click on the following link: http://lists.mysql.com/u/java/4e4f2360d44b612a/gcdmj-java=m.gmane.org This confirmation serves two purposes. First, it verifies that we are able to get mail through to you. Second, it protects you in case someone forges a subscription request in your name. We haven't checked whether your address is currently on the mailing list. To see what address you used to subscribe, look at the messages you are receiving from the mailing list. Each message has your address hidden inside its return path; for example, john&lt; at &gt;example.com receives messages with return path: java-return-&lt;number&gt;-john=example.com&lt; at &gt;lists.mysql.com. --- Administrative commands for the java list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: &lt;java-subscribe&lt; at &gt;lists.mysql.com&gt; To remove your address from the list, just send a message to the address in the ``List-Unsubscribe'' header of any list message. If you haven't changed addresses since subscribing, you can also send a message to: &lt;java-unsubscribe&lt; at &gt;lists.mysql.com&gt; or for the digest to: &lt;java-digest-unsubscribe&lt; at &gt;lists.mysql.com&gt; For addition or removal of addresses, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete the transaction. If you need to get in touch with the human owner of this list, please send a message to: &lt;java-owner&lt; at &gt;lists.mysql.com&gt; Please include a FORWARDED list message with ALL HEADERS intact to make it easier to help you. --- Enclosed is a copy of the request I received. Received: (qmail 742 invoked by uid 48); 20 Aug 2011 03:00:48 -0000 Date: 20 Aug 2011 03:00:48 -0000 Message-ID: &lt;20110820030048.741.qmail&lt; at &gt;lists.mysql.com&gt; To: java-unsubscribe-gcdmj-java=m.gmane.org&lt; at &gt;lists.mysql.com Subject: Unsubscribe request From: &lt;gcdmj-java&lt; at &gt;m.gmane.org&gt; This message was generated because of a request from 80.239.243.133. </pre> java-help< at >lists.mysql.com 2011-08-20T03:00:48 http://comments.gmane.org/gmane.comp.db.mysql.java/5507 <pre>To confirm that you would like gcdmj-java&lt; at &gt;m.gmane.org removed from the java mailing list, please click on the following link: http://lists.mysql.com/u/java/4e4f2343ed93b80b/gcdmj-java=m.gmane.org This confirmation serves two purposes. First, it verifies that we are able to get mail through to you. Second, it protects you in case someone forges a subscription request in your name. We haven't checked whether your address is currently on the mailing list. To see what address you used to subscribe, look at the messages you are receiving from the mailing list. Each message has your address hidden inside its return path; for example, john&lt; at &gt;example.com receives messages with return path: java-return-&lt;number&gt;-john=example.com&lt; at &gt;lists.mysql.com. --- Administrative commands for the java list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: &lt;java-subscribe&lt; at &gt;lists.mysql.com&gt; To remove your address from the list, just send a message to the address in the ``List-Unsubscribe'' header of any list message. If you haven't changed addresses since subscribing, you can also send a message to: &lt;java-unsubscribe&lt; at &gt;lists.mysql.com&gt; or for the digest to: &lt;java-digest-unsubscribe&lt; at &gt;lists.mysql.com&gt; For addition or removal of addresses, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete the transaction. If you need to get in touch with the human owner of this list, please send a message to: &lt;java-owner&lt; at &gt;lists.mysql.com&gt; Please include a FORWARDED list message with ALL HEADERS intact to make it easier to help you. --- Enclosed is a copy of the request I received. Received: (qmail 608 invoked by uid 48); 20 Aug 2011 03:00:19 -0000 Date: 20 Aug 2011 03:00:19 -0000 Message-ID: &lt;20110820030019.607.qmail&lt; at &gt;lists.mysql.com&gt; To: java-unsubscribe-gcdmj-java=m.gmane.org&lt; at &gt;lists.mysql.com Subject: Unsubscribe request From: &lt;gcdmj-java&lt; at &gt;m.gmane.org&gt; This message was generated because of a request from 80.239.243.133. </pre> java-help< at >lists.mysql.com 2011-08-20T03:00:19 http://comments.gmane.org/gmane.comp.db.mysql.java/5506 <pre>Hello all. MySQL Connector/MXJ 5.0.12 is now available for download. MySQL Connector/MXJ 5.0.12 is a Java utility package for deploying and managing a MySQL RDBMS. The 5.0.12 version includes MySQL 5.5.9 server community binaries and related resources for the following platforms: * Linux x86, x86_64 * Mac OS X x86, x86_64 * Windows XP/2K/NT/Vista/2003/2008/7 x86, x86_64 * SunOS sparc, x86, x86_64 * FreeBSD x86, x86_64 Platforms can easily be added or removed from: mysql-connector-mxj-gpl-5-0-12-db-files.jar MySQL Connector/MXJ may be bundled into an existing Java application and managed as a POJO (Plain Old Java Object) or launched by creating a Connector/J connection. This makes it easy for Java developers creating an application that uses JDBC through MySQL Connector/J to deploy applications which require a database by reducing installation barriers for their end-users. Adding a MySQL database to a Java application can be as easy as: 1) configuring the CLASSPATH to include: * Connector/J 5.x JDBC driver (mysql-connector-java-5.1.15-bin.jar) * Connector/MXJ classes (mysql-connector-mxj-gpl-5-0-12.jar) * Connector/MXJ resources (mysql-connector-mxj-gpl-5-0-12-db-files.jar) 2) create a JDBC connection string specifying where to deploy the physical files "server.basedir", and whatever additional connection parameters to pass to Connector/J or Connector/MXJ to refine the behavior: String url = "jdbc:mysql:mxj://localhost:3306/" + dbName // + "?" + "server.basedir=" + databaseDir // + "&amp;" + "createDatabaseIfNotExist=true"// + "&amp;" + "server.initialize-user=true" // ; With Connector/J 5.x, simply adding "mxj:" will signal the Connector/J JDBC driver to automatically deploy and launch the MySQL database with the first connection. In order for MySQL Connector/MXJ to make the MySQL database appear to be a java-based component, it determines what platform the system is running on, selects the appropriate binary, and launches the executable. It will also optionally deploy an initial database, with any specified parameters. Included is a Connector/J URL example: ConnectorMXJUrlTestExample.java and a POJO usage example: ConnectorMXJObjectTestExample.java Each are located in the top level of mysql-connector-mxj-gpl-5-0-12.jar and the source is in the src/ directory. Documentation: http://dev.mysql.com/doc/refman/5.5/en/connector-mxj.html You can download Connector/MXJ sources and binaries from: http://dev.mysql.com/downloads/connector/mxj/5.0.html You can download the latest Connector/J JDBC driver from: http://dev.mysql.com/downloads/connector/j/5.1.html Remember, feedback is welcome and encouraged. Please send questions/comments to java&lt; at &gt;lists.mysql.com </pre> Tonci Grgin 2011-07-07T17:22:12 http://comments.gmane.org/gmane.comp.db.mysql.java/5505 <pre>Hello all, MySQL Connector/J 5.1.17, a maintenance release of the production 5.1 branch has been released. Connector/J is the Type-IV pure-Java JDBC driver for MySQL. Version 5.1.17 is suitable for use with any MySQL version including MySQL-5.1 or MySQL-5.5. It is now available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories and MOS. As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.: http://forge.mysql.com/wiki/Contributing MySQL Connector/J 5.1.17 includes the following general bug fixes and improvements: - Fix for Bug#61332 - LIKE not optimized in server when run against I__S tables and no wildcards used. Databases/tables with "_" and/or "%" in their names (escaped or not) will be handled by this code path, although slower, since it's rare to find these characters in table names in SQL. If there's a "_" or "%" in the string, LIKE will take care of that, otherwise we now use = . The only exception is information_schema database which is handled separately. Patch covers both getTables() and getColumns(). - Fix for Bug#61150 - First call to stored procedure fails with "No Database Selected". The workaround introduced in DatabaseMetaData.getCallStmtParameterTypes to fix the bug in server where SHOW CREATE PROCEDURE was not respecting lower-case table names is misbehaving when connection is not attached to database and on non-casesensitive OS. - Fix for Bug#61105 - Avoid a concurrent bottleneck in Java's character set encoding/decoding when converting bytes to/from Strings. * IMPORTANT NOTE * No longer use String.getBytes(...), or new String(byte[]...), use the StringUtils method instead. Enjoy! Tonci </pre> Tonci Grgin 2011-07-07T17:07:30 http://comments.gmane.org/gmane.comp.db.mysql.java/5502 <pre>Folks, I am compiling within the Eclipse IDE. Within com.mysql.jdbc.CallableStatement the implented java.sql.CallableStatement results in the following error “The type CallableStatement must implement the inherited abstract method CallableStatement.getNString(int)” Is there something that I am missing? regards, Kevin</pre> Kevin Hine 2011-05-24T09:47:41 http://comments.gmane.org/gmane.comp.db.mysql.java/5501 <pre>Hello, While testing my application with MySQL I noticed a difference with Oracle's JDBC implementation. In the following excerpt, I expect the call to getString to return the "new-value" /* Sometimes the application calls moveToInsertRow() to insert a new row or next() to update an existing row in the database */ ... resultSet.updateString(2,"new-value"); resultSet.getString(2).equals("new-value"); ... /* Sometimes the database does not need to be updated and the changes are canceled */ It works as expected when inserting a new row (calling resultSet.moveToInsertRow() before the two lines above). However, it does not work when updating a row (calling resultSet.next() before the the two lines above). In this case the call to getString still returns the value in the database. Is there a way to make getString after updateString to work consistently for both uses case? Thank You, Dmitry Sample Code: import java.sql.Connection; import java.sql.DriverManager; import java.sql.ResultSet; import java.sql.SQLException; import java.sql.Statement; import com.mysql.jdbc.util.BaseBugReport; public class BugReportVisibilityOfUpdate extends BaseBugReport { Connection con; Statement stm; public BugReportVisibilityOfUpdate() { super(); } public void setUp() throws Exception { con = DriverManager.getConnection(getUrl()); stm = con.createStatement(); stm.executeUpdate("CREATE TABLE bug (id INTEGER UNSIGNED NOT NULL,value VARCHAR(25), PRIMARY KEY(id));"); stm.executeUpdate("INSERT INTO bug(id,value) VALUES(1,'current-value')"); } public void tearDown() throws Exception { con = DriverManager.getConnection(getUrl()); stm = con.createStatement(); stm.executeUpdate("DROP TABLE bug"); stm.close(); } public void runTest() throws Exception { con = DriverManager.getConnection(getUrl()); stm = con.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE); ResultSet rs = null; /* Test Case 1 - Passed. In the rs.moveToInsertRow test, calling getString after updateString works as expected */ try { rs = stm.executeQuery("SELECT id, value from bug where id = '2'"); rs.moveToInsertRow(); assertTrue("Before update getString should return null", rs.getString(2)==null); rs.updateString("value", "new-value"); assertTrue("After update should return 'new-value'", rs.getString(2).equals("new-value")); rs.close(); } catch (SQLException e) { System.err.println("SQLException: " + e.getMessage()); } /* Test Case 2 - Failed. In the rs.next test, calling getString after updateString still returns the value from the database instead of the value used in the updateString */ try { rs = stm.executeQuery("SELECT id, value from bug where id = '1'"); rs.next(); assertTrue("Before update getString should return 'current-value'", rs.getString(2).equals("current-value")); rs.updateString("value", "new-value"); /* The following assert failes. Oracle returns the "new-value" */ assertTrue("After update should return 'new-value'", rs.getString(2).equals("new-value")); rs.close(); } catch (SQLException e) { System.err.println("SQLException: " + e.getMessage()); } } public static void main(String[] args) throws Exception { (new BugReportVisibilityOfUpdate()).run(); } } </pre> Dmitry Isakbayev 2011-05-10T19:26:49 http://comments.gmane.org/gmane.comp.db.mysql.java/5500 <pre>Hi All, We are frequently getting DBCP error. We have seen this error in catalina.log &amp; apps log. This issue has started since last 2 -3 days. We have checked the application code when this error has occured and assure that there is no connection leakage in code. Mysql server is also running fine. We have tune memory parameters in mysql, however effectless. Still we are getting the same error. Any suggestion/solution would be appreciated. Mysql server version: 5.0.45 JDBC version: mysql-connector-java-5.1.5-bin.jar apache Tomcat version: 6.0.16 server.xml parameters are as follows:: url="jdbc:mysql://hostname:3306/dbname" username="user" password="pass" maxActive="40" maxIdle="20" maxWait="5000" ERROR: 2011-05-05 16:32:57,666 [ajp-8009-177] ERROR TrainSearchResultCache.java - Error retrieving Train Search from DB: s- org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:104) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) at com.eos.gds.data.DatabaseManager.getConnection(DatabaseManager.java:73) at com.eos.gds.data.DatabaseManager.getConnection(DatabaseManager.java:60) ............................................ Caused by: java.util.NoSuchElementException: Timeout waiting for idle object at org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:958) at org.apache.tomcat.dbcp.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:84) at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96) ... 28 more com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure Last packet sent to the server was 24 ms ago. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2873) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2763) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3299) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1837) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1961) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2543) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1737) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2022) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1940) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1925) at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) at com.eos.gds.cache.FareQuoteDBCache.storeItinQuotesIntoPresistentCache(FareQuoteDBCache.java:1029) at com.eos.gds.cache.FareQuoteDBCache.processInputQueue(FareQuoteDBCache.java:899) at com.eos.gds.cache.FareQuoteDBCache.access$000(FareQuoteDBCache.java:37) at com.eos.gds.cache.FareQuoteDBCache$1.run(FareQuoteDBCache.java:103) at java.lang.Thread.run(Thread.java:619) Caused by: java.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.mysql.jdbc.util.ReadAheadInputStream.fill(ReadAheadInputStream.java:113) at com.mysql.jdbc.util.ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(ReadAheadInputStream.java:160) at com.mysql.jdbc.util.ReadAheadInputStream.read(ReadAheadInputStream.java:188) at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2329) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2774) </pre> Dhaval Jaiswal 2011-05-06T07:56:13 http://comments.gmane.org/gmane.comp.db.mysql.java/5499 <pre>hi all, iam developing mobile agent using aglet 2.0.2 and mysql-connector-java-5.1.14 to connect database mysql. i was create simple code to insert some data to database. then i compile it and its work, but when i running with tahiti server there is error and no data insert to my database. anyone know the problem?? regards, scifo *this is error message in console:* database failure: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driv er has not received any packets from the server. *this is source code :* public void run() { System.out.println("Tampil no pencarian"); String mysqldriver = "com.mysql.jdbc.Driver"; Connection conn = null; Statement st = null; ResultSet rset = null; String sqlQuery = "INSERT INTO `cobadb`.`customer` (`nama` ,`alamat` ,`umur` ,`email` ,`telepon`) VALUES ( 'dudul', 'tegal', '21', ' dudul&lt; at &gt;yahoo.com', '12234567')"; try { Class.forName(mysqldriver); // koneksi driver database conn = DriverManager.getConnection("jdbc:mysql://localhost/cobadb","root","scifoanggi"); // koneksi ke mySQL st = conn.createStatement(); rset = st.executeUpdate(sqlQuery); // ekseskusi quey SQL } catch(ClassNotFoundException e) { System.err.println("drive failure: " + e.getMessage()); } catch (SQLException e) { System.err.println("database failure: "+ e.getMessage()); } finally { try { if (rset !=null) rset.close(); } catch (SQLException sqle) {} try { if (st != null ) st.close(); } catch (SQLException sqle) {} try { if (conn != null ) conn.close(); } catch (SQLException sqle) {} } } </pre> scifo anggy yudianto 2011-04-28T10:01:07 http://comments.gmane.org/gmane.comp.db.mysql.java/5497 <pre>Hi, would it be possible to upload Connector/MXJ to the maven repository ? I'd be happy to help with this (via https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central) if you need a volunteer ? cheers, Thomas Dudziak </pre> Thomas Dudziak 2011-02-12T01:18:15 http://comments.gmane.org/gmane.comp.db.mysql.java/5496 <pre>Hi, MySQL Connector/J 5.1.15, a maintenance release of the production 5.1 branch has been released. Connector/J is the Type-IV pure-Java JDBC driver for MySQL. Version 5.1.15 is suitable for use with any MySQL version including MySQL-5.1 or MySQL-5.5. It is now available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories (note that not all mirror sites or repositories may be up to date at this point of time - if you can't find this version on some mirror, please try again later or choose another download site.) As always, we recommend that you check the change log http://dev.mysql.com/doc/refman/5.1/en/cj-news.html and "Upgrading" sections http://dev.mysql.com/doc/refman/5.1/en/cj-upgrading.html in the manual before upgrading as well as the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.: http://forge.mysql.com/wiki/Contributing MySQL Connector/J 5.1.15 includes the following general bug fixes and improvements: - Fix for Bug#38367, parameters metadata did not reflect the fact that NULL is allowed parameter value. So DatabaseMetaData.getProcedureColumns will set isNullable member to java.sql.DatabaseMetaData.procedureNullable now. - Fix for Bug#27916, DatabaseMetaData.getTypeInfo() does not return all the available data types. - Fix for Bug#59224, adding 5.5 reserved words to DatabaseMetaData.getSQLKeywords(). - Fixed an issue where statement comments set via Connection.setStatementComment() weren't represented in autoGenerateTestcaseScript=true output. - Added ability to include the current java thread dump in the exception message given for deadlock/wait lock timeout exceptions, enable with "includeThreadDumpInDeadlockExceptions=true" in your JDBC url. - Added ability to include current thread name as a statement comment visible in MySQL's "SHOW PROCESSLIST" and Innodb deadlock diagnostics, enable with "includeThreadNamesAsStatementComment=true". - Added an SLF4J logging adapter. Enable by adding setting the connection property "logger" to "Slf4JLogger" and placing the appropriate bridge from SLF4J to the logging framework of choice in your CLASSPATH. As with other Connector/J logging adapters, the log category name used by the driver is "MySQL". See http://www.slf4j.org/manual.html for more details. Enjoy! -Mark </pre> Mark Matthews 2011-02-10T14:55:14 http://comments.gmane.org/gmane.comp.db.mysql.java/5495 <pre> Hi, Production Database have been migrated from old to new one as per application requirement with additional columns and tables. And hence has to be validated that the migrated data is correct by creating a script to run written in java. how to compare 2 columns(different col_name) in 2 different databases placed at different server and display output( in excel format) using JAVA. If matched, return TRUE else display unmatched with column id,column_name, table name. Any help will be greatly appreciated. "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." www.cybage.com </pre> Reshma Parveen 2010-12-22T08:12:05 http://comments.gmane.org/gmane.comp.db.mysql.java/5494 <pre>Hi, Production Database have been migrated from old to new one as per application requirement with additional columns and tables. And hence has to be validated that the migrated data is correct by creating a script to run written in java. how to compare 2 columns(different col_name) in 2 different databases placed at different server and display output( in excel format) using JAVA. If matched, return TRUE else display unmatched with column id,column_name, table name. Any help will be greatly appreciated. "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." www.cybage.com </pre> Reshma Parveen 2010-12-22T07:58:53 http://comments.gmane.org/gmane.comp.db.mysql.java/5493 <pre>Hi everybody, I'm developping a Java application which uses data stored in a MySQL Community Server running on my computer. Now I want to use the Connector/MXJ to have an embedded database in my application. To do this I follow this procedure http://dev.mysql.com/doc/refman/5.0/en/connector-mxj-usagenotes-customdb.html. The following Jar files are in the classpath - mysql-connector-java-5.1.13-bin.jar - mysql-connector-mxj-db-gpl-5.0.11.jar - mycustom-mysql-connector-mxj-db-gpl-5.0.11-files.jar - aspectjrt.jar The problem is when I when I run my Java application I'have got the following error messages : [C:\Users\sebastien\AppData\Local\Temp\mysql-c.mxj\bin\mysqld.exe][--no-defaults][--console][--port=3336][--socket=mysql.sock][--basedir=C:\Users\sebastien\AppData\Local\Temp\mysql-c.mxj][--datadir=C:\Users\sebastien\AppData\Local\Temp\mysql-c.mxj\data][--pid-file=C:\Users\sebastien\AppData\Local\Temp\mysql-c.mxj\data\MysqldResource.pid] [MysqldResource] launching mysqld (driver_launched_mysqld_1) [MysqldResource] mysqld running as process: 3404 101208 11:14:12 [Note] Plugin 'FEDERATED' is disabled. InnoDB: Error: log file .\ib_logfile0 is of different size 0 25165824 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 101208 11:14:12 [ERROR] Plugin 'InnoDB' init function returned error. 101208 11:14:12 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 101208 11:14:13 [Note] Event Scheduler: Loaded 0 events 101208 11:14:13 [Note] C:\Users\sebastien\AppData\Local\Temp\mysql-c.mxj\bin\mysqld.exe: ready for connections. Version: '5.1.40-community' socket: '' port: 3336 MySQL Community Server (GPL) com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown table engine 'InnoDB' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:409) at com.mysql.jdbc.Util.getInstance(Util.java:384) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3566) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3498) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1959) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2113) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2568) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2113) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2409) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2327) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2312) at worker.WorkerDb.clean(WorkerDb.java:774) at controller.Controller.clean(Controller.java:64) at controller.Controller.updateAll(Controller.java:52) at controller.Controller.&lt;init&gt;(Controller.java:45) at main.Main.main(Main.java:24) Thanks for your advices! sébastien </pre> Sébastien Grognuz 2010-12-13T09:31:56 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.db.mysql.java