empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] Closed: (EMPIREDB-34) Add support for stmt.executeUpdate with Statement.RETURN_GENERATED_KEYS instead of getPostInsertAutoIncValue()
Date Tue, 17 Mar 2009 22:25:50 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rainer Döbele closed EMPIREDB-34.
---------------------------------

    Resolution: Fixed

Resolved

> Add support for stmt.executeUpdate with Statement.RETURN_GENERATED_KEYS instead of getPostInsertAutoIncValue()
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: EMPIREDB-34
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-34
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: empire-db-2.0.5-incubating
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>             Fix For: empire-db-2.0.5-incubating
>
>
> So far Empire-db has used mainly native or emulated Sequences for record key generation.
> For databases that auto generate keys there has been a method called getPostInsertAutoIncValue()
which had to be implmented for each driver. 
> The ability of JDBC to retrieve auto generated keys when executing a statement has not
been used.
> In order to support more databased the getPostInsertAutoIncValue()  proved to be too
inflexible.
> Instead it is desireable to use the getGeneratedKeys() function on the JDBC Statement
object.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message