[
http://issues.apache.org/jira/browse/DERBY-1500?page=comments#action_12429195 ]
Knut Anders Hatlen commented on DERBY-1500:
---
Derby Network Client and JCC already work correctly. I will fix the embedded
driver.
I updated the JDBC 4 spec data conversion tables for Short and Byte so
I would add support for them when u can
-lance
Markus Fuchs (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1500?page=comments#action_12424627 ]
Markus Fuchs commented on DERBY-1500:
[
http://issues.apache.org/jira/browse/DERBY-1500?page=comments#action_12424612 ]
Markus Fuchs commented on DERBY-1500:
-
Hi Daniel,
1) java.lang.Short is not a valid object mapping for SMALLINT:
Why do I get the same exception on
[
http://issues.apache.org/jira/browse/DERBY-1500?page=comments#action_12424621 ]
Daniel John Debrunner commented on DERBY-1500:
--
Markus wrote:
Also, why does stmnt.setShort(1, Short.valueOf(0)) work in this case?
Because that's
[
http://issues.apache.org/jira/browse/DERBY-1500?page=comments#action_12424627 ]
Markus Fuchs commented on DERBY-1500:
-
This behavior is apparantly implemented by many major database vendors, e.g.
Oracle, SQLServer, Sybase, and the Derby
I am not sure why java.lang.Short is not covered in the conversion
tables in the JDBC spec. Probably an oversite or just a spec bug. It
is reasonable to be supported since the other conversions are
supported.
I will discuss with the EG.
Markus Fuchs (JIRA) wrote:
[
[
http://issues.apache.org/jira/browse/DERBY-1500?page=comments#action_12421943 ]
Daniel John Debrunner commented on DERBY-1500:
--
java.lang.Short is not a valid object mapping for SMALLINT, JDBC defines the
mapping as
