Bug #7715 Timestamps converted incorrectly to strings with SSPS and Upd. Result Sets.
Submitted: 6 Jan 2005 20:33 Modified: 6 Jan 2005 20:58
Reporter: Mark Matthews Email Updates:
Status: Closed Impact on me:
Category:Connector / J Severity:S3 (Non-critical)
Version:3.1 and newer OS:
Assigned to: Mark Matthews CPU Architecture:Any

[6 Jan 2005 20:33] Mark Matthews
When using server-side prepared statements with timestamps, _and_ when asking for an updatable result set, the JDBC driver incorrectly converts the nanos portion of the timestamp when converting to a stringified form, using 0x00 instead of '0', causing parsing to fail.

How to repeat:
public void testConvertedBinaryTimestamp() throws Exception {
    	PreparedStatement pStmt = null;
    	try {
    		this.stmt.executeUpdate("DROP TABLE IF EXISTS testConvertedBinaryTimestamp");
    		this.stmt.executeUpdate("CREATE TABLE testConvertedBinaryTimestamp (field1 VARCHAR(32), field2 VARCHAR(32), field3 VARCHAR(32), field4 TIMESTAMP)");
    		this.stmt.executeUpdate("INSERT INTO testConvertedBinaryTimestamp VALUES ('abc', 'def', 'ghi', NOW())");
    		pStmt = this.conn.prepareStatement("SELECT field1, field2, field3, field4 FROM testConvertedBinaryTimestamp", 
    		this.rs = pStmt.executeQuery();
    		this.rs.getObject(4)); // fails if bug exists	
    	} finally {
    		this.stmt.executeUpdate("DROP TABLE IF EXISTS testConvertedBinaryTimestamp");