db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-773) PreparedStatement doesn't like Character objects when using setObject with jdbc types CHAR/VARCHAR
Date Sun, 18 Dec 2005 20:30:35 GMT
    [ http://issues.apache.org/jira/browse/DERBY-773?page=comments#action_12360752 ] 

Thomas Dudziak commented on DERBY-773:
--------------------------------------

Ok, I won't press you any further. But you are probably aware of the flaw in that argumentation.
Users stay with databases for their features, not the easiness of converting to other databases.
Not to mention that most other databases are able to do more than what the JDBC spec says
they have to do at the least in order to be compliant.

> PreparedStatement doesn't like Character objects when using setObject with jdbc types
CHAR/VARCHAR
> --------------------------------------------------------------------------------------------------
>
>          Key: DERBY-773
>          URL: http://issues.apache.org/jira/browse/DERBY-773
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.1.2.1
>  Environment: Windows XP
> Java 1.5
> Derby in Embedded or Network mode
>     Reporter: Thomas Dudziak

>
> When using 
>     PreparedStatement ps = ...
>     Character value = ...
>     ps.setObject(0, value, Types.CHAR);
> or
>     ps.setObject(0, value, Types.VARCHAR);
> Derby complains with
>     "An attempt was made to get a data value of type 'VARCHAR' from a data value of type
'java.lang.Character'."
> Currently a workaround with
>     ps.setObject(0, value.toString(), Types.CHAR);
> is necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message