db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1316) Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()
Date Thu, 11 May 2006 20:29:10 GMT
    [ 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:
>     Reporter: Rick Hillegas
>      Fix For:

> 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:
For more information on JIRA, see:

View raw message