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 "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/05/11 03:35:05 UTC
[jira] Created: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
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, which was added in JDBC4. 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
Re: [jira] Created: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Lance J. Andersen" <La...@Sun.COM>.
This method was not added in JDBC 4, it was added in JDBC 3 (I would
have picked a more articulate name as i find the name a bit confusing as
do others)
Rick Hillegas (JIRA) wrote:
> 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, which was added in JDBC4. 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.
>
>
[jira] Updated: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1316?page=all ]
Rick Hillegas updated DERBY-1316:
---------------------------------
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()
> -------------------------------------------------------------
>
> Key: DERBY-1316
> URL: http://issues.apache.org/jira/browse/DERBY-1316
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
> Fix For: 10.2.3.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
[jira] Commented: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1316?page=all ]
Rick Hillegas updated DERBY-1316:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()
> -------------------------------------------------------------
>
> Key: DERBY-1316
> URL: http://issues.apache.org/jira/browse/DERBY-1316
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.0
> Reporter: Rick Hillegas
> Fix For: 10.2.2.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
[jira] Resolved: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-1316.
-----------------------------------
Resolution: Duplicate
Duplicate of DERBY-2789
> Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()
> -------------------------------------------------------------
>
> Key: DERBY-1316
> URL: https://issues.apache.org/jira/browse/DERBY-1316
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-1316.
----------------------------------
DatabaseMetaData.locatorsUpdateCopy() now returns 'true'.
See DERBY-2789 for details.
> Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()
> -------------------------------------------------------------
>
> Key: DERBY-1316
> URL: https://issues.apache.org/jira/browse/DERBY-1316
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1316?page=all ]
Rick Hillegas updated DERBY-1316:
---------------------------------
Description: 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. (was: Both the embedded and network implementations of DatabaseMetaData return the wrong value for this method, which was added in JDBC4. 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.)
Lance has corrected the bug description: this method was added in JDBC3, not JDBC4.
> 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
[jira] Updated: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1316?page=all ]
Rick Hillegas updated DERBY-1316:
---------------------------------
Urgency: Low
> Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()
> -------------------------------------------------------------
>
> Key: DERBY-1316
> URL: http://issues.apache.org/jira/browse/DERBY-1316
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects 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
[jira] Commented: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1316?page=comments#action_12379136 ]
Rick Hillegas commented on DERBY-1316:
--------------------------------------
Lance adds:
"All DatabaseMetaDataMethods must be implemented. Unfortunately the previous authors of the spec did not take into account that some backends do not support LOB so this should not have been a boolean.
I would probably return true as Derby is not locator based."
> 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
[jira] Commented: (DERBY-1316) Wrong value returned by
DatabaseMetaData.locatorsUpdateCopy()
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ 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