Message
From: Amita Vadhavkar [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; tuscany-dev@ws.apache.org
Sent: Tuesday, July 24, 2007 8:56:36 AM
Subject: Re: Flexibility in supporting JDBC's
Statement.RETURN_GENERATED_KEYS in RDB DAS (JIRA-1417)
Hi,
Below are some details about the solution for JIRA-1353
Hi,
Below are some details about the solution for JIRA-1353.
Please review the patch.
http://issues.apache.org/jira/browse/DERBY-242 - indicates that for 10.1.1.0,
DatabaseMetadata.supportsGetGeneratedKeys() returns false. Also, checked
that for the current Maven Repo's Derby version (10.1.2.1)
...
- Ron
- Original Message
From: Amita Vadhavkar [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; tuscany-dev@ws.apache.org
Sent: Tuesday, July 24, 2007 8:56:36 AM
Subject: Re: Flexibility in supporting JDBC's Statement.RETURN_GENERATED_KEYS
in RDB DAS (JIRA-1417)
Hi,
Below are some details
Hi Amita
Indeed we need a better way to handle this, my only concern with
this approach are the unknown side effects we can get if the exception
returned when you first pass the Statement.RETURN_GENERATED_KEYS is
not related to the JDBC driver supporting or not generated keys.
On 7/9/07,
That is right, I will also give it a try with some known rdbms dirvers,
versions and list the results in JIRA-1417, and we will also analyze further
for alternatives.
I also, saw some relevant links related to JIRA-1416 (PostgreSQL...generated
keys).
[1]
It would be great if you could force a different exception in your
investigation (e.g jdbc driver supports returning the generated keys,
but the call gives back a different exception), and see what is the
resulted behavior of your proposal.
On 7/10/07, Amita Vadhavkar [EMAIL PROTECTED] wrote:
Hi,
We are at present hardcoding some vendors (e.g. Oracle) in ConnectionImpl to
decide whether to
use autogenerated key feature in preparedStatement. This logic is subject to
change
as and when new features are supported by different databases and different
vendors.
Instead, if we have a
