You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/05/11 19:56:07 UTC
[jira] Commented: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
[ http://issues.apache.org/jira/browse/DERBY-1316?page=comments#action_12379114 ]
Daniel John Debrunner commented on DERBY-1316:
----------------------------------------------
Returning 'true' for embedded is misleading as well, since no update methods are supported it is not true that 'locatorsUpdateCopy'. Probably a case where a not implemented exception should have been thrown in embedded.
If DERBY-1286 is fixed to match the client then I would agree returning 'true' is correct.
> 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