Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <9867184.1152646954652.JavaMail.jira@brutus>
Date: Tue, 11 Jul 2006 19:42:34 +0000 (GMT+00:00)
From: "Satheesh Bandaram (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-242)
 DatabaseMetaData.supportsGetGeneratedKeys needs to return FALSE, since
 Derby only has limited support.
In-Reply-To: <1350636386.1114562363875.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-242?page=all ]
     
Satheesh Bandaram closed DERBY-242:
-----------------------------------


Fix has been in the codeline for sometime.

> DatabaseMetaData.supportsGetGeneratedKeys needs to return FALSE, since Derby only has limited support.
> ------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-242
>          URL: http://issues.apache.org/jira/browse/DERBY-242
>      Project: Derby
>         Type: Bug

>   Components: JDBC
>     Versions: 10.0.2.0
>  Environment: ALL
>     Reporter: Satheesh Bandaram
>     Assignee: Lance Andersen
>      Fix For: 10.1.1.0

>
> Derby only has partial support for retrieving generated values. 
> Because of this, it is desirable to make 
> DatabaseMetaData.supportsGetGeneratedKeys return FALSE. One 
> of the restrictions include Jira entry Derby-201. Till this is 
> fixed, we should change derby to return FALSE for this.
> This would also match Derby client behavior. 

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