Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Thu, 11 May 2006 10:34:21 -0400
From: "Lance J. Andersen" <Lance.Andersen@Sun.COM>
Subject: Re: [jira] Created: (DERBY-1316) Wrong value returned by
 DatabaseMetaData.locatorsUpdateCopy()
In-reply-to: <18869824.1147311305086.JavaMail.jira@brutus>
Sender: Lance.Andersen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44634B6D.4060307@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT
References: <18869824.1147311305086.JavaMail.jira@brutus>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)

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.
>
>