Mailing-List: contact empire-db-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@incubator.apache.org
Message-ID: <1728131680.1234090620370.JavaMail.jira@brutus>
Date: Sun, 8 Feb 2009 02:57:00 -0800 (PST)
From: =?utf-8?Q?Rainer_D=C3=B6bele_=28JIRA=29?=
 <empire-db-dev@incubator.apache.org>
To: empire-db-commits@incubator.apache.org
Subject: [jira] Created: (EMPIREDB-34) Add support for stmt.executeUpdate
 with Statement.RETURN_GENERATED_KEYS instead of getPostInsertAutoIncValue()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Add support for stmt.executeUpdate with Statement.RETURN_GENERATED_KEYS ins=
tead 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=C3=B6bele
            Assignee: Rainer D=C3=B6bele
             Fix For: empire-db-2.0.5-incubating


So far Empire-db has used mainly native or emulated Sequences for record ke=
y generation.
For databases that auto generate keys there has been a method called getPos=
tInsertAutoIncValue() which had to be implmented for each driver.=20
The ability of JDBC to retrieve auto generated keys when executing a statem=
ent 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.


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