[ 
https://issues.apache.org/jira/browse/DERBY-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538087
 ] 

Mamta A. Satoor commented on DERBY-2105:
----------------------------------------

I tried the test case in Embedded mode (the earlier results were from running 
the program in client server mode) and similar (not exactly the same) is thrown 
in Embedded configuration too (again, this is by testing the supplied sample 
code against Derby 1.4 using Sun's jdk142)
 
$ java org.apache.derbyTesting.functionTests.tests.lang.DBMetaData2
Exception in thread "main" java.sql.SQLException: An attempt was made to get a 
data value of type 'CHAR' from a data value of type 'java.sql.Clob'.
        at 
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:88)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:94)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:180)
        at 
org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(EmbedConnection.java:2238)
        at 
org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(ConnectionChild.java:154)
        at 
org.apache.derby.impl.jdbc.EmbedResultSet.dataTypeConversion(EmbedResultSet.java:4522)
        at 
org.apache.derby.impl.jdbc.EmbedResultSet.updateClob(EmbedResultSet.java:4154)
        at 
org.apache.derby.impl.jdbc.EmbedResultSet.updateObject(EmbedResultSet.java:3144)
        at 
org.apache.derby.impl.jdbc.EmbedResultSet20.updateObject(EmbedResultSet20.java:210)
        at 
org.apache.derbyTesting.functionTests.tests.lang.DBMetaData2.main(DBMetaData2.java:200)

> Network Client - Column of type CHAR, VARCHAR or LONG VARCHAR contains wrong 
> value after being updated using the updateObject() method with a clob as 
> parameter.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2105
>                 URL: https://issues.apache.org/jira/browse/DERBY-2105
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>            Reporter: Fernanda Pizzorno
>
> REPRO:
>             Statement stmt1 = 
> conn.createStatement(ResultSet.TYPE_FORWARD_ONLY, 
>                     ResultSet.CONCUR_UPDATABLE);
>             Statement stmt2 = conn.createStatement();
>             stmt1.executeUpdate("CREATE TABLE t1 (i int, c char(60))");
>             stmt1.executeUpdate("CREATE TABLE t2 (i int, c clob(1K))");
>             stmt1.executeUpdate("INSERT INTO t1 values (1, 'xx')");
>             stmt1.executeUpdate("INSERT INTO t2 values (1, 'yy')");
>             ResultSet rs1 = stmt1.executeQuery("SELECT * FROM t1");
>             ResultSet rs2 = stmt2.executeQuery("SELECT * FROM t2");
>             if (!rs1.next()) {
>                 System.out.println("Row not found");
>                 return;
>             }
>             if (!rs2.next()) {
>                 System.out.println("Row not found");
>                 return;            
>             }
>             rs1.updateObject(2, rs2.getClob(2));
>             rs1.updateRow();
>             rs1.close();
>             rs1 = stmt1.executeQuery("SELECT * FROM t1");
>             if (!rs1.next()) {
>                 System.out.println("Row not found");
>                 return;
>             }
>             if (!rs2.getString(2).equals(rs1.getString(2))) {
>                 System.out.println("FAIL - wrong value for column 2 expected: 
> " + 
>                         rs2.getString(2) + " but was: " + rs1.getString(2));
>             }
>             rs1.close();
>             rs2.close();        
>             stmt1.close();
>             stmt2.close();
> OUTPUT:
> FAIL - wrong value for column 2 expected: yy but was: [EMAIL PROTECTED]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to