Hi Lance,
Dan points out the neither true nor false is a satisfying return value
from this method for our embedded implementation: our embedded
implementation doesn't even implement the set() methods on Clob/Blob.
And the javadoc doesn't seem to countenance throwing
SQLFeatureNotSupportedException. What are your thoughts?
Thanks,
-Rick
--- Begin Message ---
[
http://issues.apache.org/jira/browse/DERBY-1316?page=comments#action_12379131 ]
Rick Hillegas commented on DERBY-1316:
--------------------------------------
I see that neither true nor false is completely satisfying for the current
embedded implementation. Throwing SQLFeatureNotSupportedException is not
allowed according to the 1.6 javadoc: this is a mandatory method.
> Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()
> -------------------------------------------------------------
>
> Key: DERBY-1316
> URL: http://issues.apache.org/jira/browse/DERBY-1316
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> Reporter: Rick Hillegas
> Fix For: 10.2.0.0
>
> Both the embedded and network implementations of DatabaseMetaData return the
> wrong value for this method. This method currently returns false but should
> return true. Returning false means that your Blob/Clobs are backed by SQL
> Locators and therefore that set() methods on your Lobs write-through to the
> database.
--
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
--- End Message ---
