[ http://issues.apache.org/jira/browse/DERBY-100?page=all ]
Fernanda Pizzorno updated DERBY-100:
------------------------------------
Attachment: DERBY-100-4.diff
DERBY-100-4.stat
Thank you for looking into the patch Bryan Pendleton.
The change to the getBoolean() method that you mentioned (deleting the exit
trancing), that was an accident that happened while I was manually merging
changes. I am sorry I did not notice it before. I am attaching a patch to fix
it.
For rowInserted(), my intention was to make the implementation of this method
as similar as possible to that of the rowDeteled() and rowUpdated() methods.
Since these two methods do not have entry trancing, I removed it from the
rowInserted() method.
I have only run derbylang with this new patch since the changes where so small.
Please let me know if you think it is necessary that I run derbyall and I will
do it.
> Add support for insert functionality using JDBC 2.0 updatable resultset apis
> ----------------------------------------------------------------------------
>
> Key: DERBY-100
> URL: http://issues.apache.org/jira/browse/DERBY-100
> Project: Derby
> Type: New Feature
> Components: JDBC
> Versions: 10.1.1.0
> Reporter: Mamta A. Satoor
> Assignee: Fernanda Pizzorno
> Attachments: DERBY-100-2.diff, DERBY-100-2.stat, DERBY-100-3.diff,
> DERBY-100-3.stat, DERBY-100-4.diff, DERBY-100-4.stat, DERBY-100.diff,
> DERBY-100.stat
>
> The JDBC 2.0 API introduced the ability to update/delete/insert rows from a
> resultset using methods in the Java programming language rather than having
> to send an SQL command. This Jira entry is to track the insert rows
> functionality using JDBC 2.0 apis.
--
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
