db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance J. Andersen" <Lance.Ander...@Sun.COM>
Subject Re: [jira] Created: (DERBY-242) DatabaseMetaData.supportsGetGeneratedKeys needs to return FALSE, since Derby only has limited support.
Date Fri, 29 Apr 2005 20:33:16 GMT
I take it this is with the Embedded Driver as it looks like the code for 
the new Client Driver is returning false.

I can take this if no one else wants it.

Mamta Satoor wrote:

>I think this is a very easy bug to fix. So, if someone is looking for
>an opportunity to start with a simple bug, this will be a good one.
>On 4/26/05, Satheesh Bandaram (JIRA) <derby-dev@db.apache.org> wrote:
>>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:
>>Environment: ALL
>>   Reporter: Satheesh Bandaram
>>Assigned to: Satheesh Bandaram
>>    Fix For:
>>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

View raw message