[
https://issues.apache.org/jira/browse/DERBY-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499359
]
Myrna van Lunteren commented on DERBY-1501:
---
I don't see any particular check-in for this bug, the fix
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12421304 ]
Knut Anders Hatlen commented on DERBY-1501:
---
Lance Andersen wrote on derby-dev:
i have removed the rogue sentence in its entirety from the javadocs for
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12421145 ]
Daniel John Debrunner commented on DERBY-1501:
--
Lance Andersen wrote on the derv-dev list:
I am not sure why the wording was added to the
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12421166 ]
Knut Anders Hatlen commented on DERBY-1501:
---
Dan wrote:
So let's check this out before we change the existing
behaviour. Remember the javadoc that
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12421173 ]
Daniel John Debrunner commented on DERBY-1501:
--
Yes, sorry I got confused. I'd assumed since I'd seen some other e-mails saying
some method needed to
i have removed the rogue sentence in its entirety from the javadocs for
setNull(int,int, String) as it is not needed and is not correct in
regards to typeCode.
-lance
Daniel John Debrunner (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420620 ]
I am not sure why the wording was added to the overloaded setNull
method which was added in JDBC 3.
i probably would expect it to not ignore the specified sql type in
order to make sure the action requested is valid. I would have to
check the SQL standard and discuss this with the EG
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420549 ]
Knut Anders Hatlen commented on DERBY-1501:
---
Kristian wrote:
But what about the second issue? The embedded driver determines if
the type of the parameter is
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420620 ]
Daniel John Debrunner commented on DERBY-1501:
--
Knut Anders indicates
setNull(int,int,String)
- If a JDBC driver does not need the type code or type name
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420458 ]
Kristian Waagan commented on DERBY-1501:
The inconsistent behavior between the client and embedded driver is a bug.
But what about the second issue?
The embedded
[
http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420487 ]
Daniel John Debrunner commented on DERBY-1501:
--
Derby does support the JDBC type LONGVARBINARY, it corresponds to the SQL type
LONGVARCHAR FOR BIT DATA
See
11 matches
Mail list logo