db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-605) updatable ResultSet
Date Fri, 07 Oct 2005 16:44:49 GMT
    [ http://issues.apache.org/jira/browse/DERBY-605?page=comments#action_12331610 ] 

Dag H. Wanvik commented on DERBY-605:
-------------------------------------

In the example you provided in the bug you filed
(http://issues.apache.org/jira/browse/DERBY-605), you used
TYPE_SCROLL_INSENSITIVE. This would give extra isolation (think
snapshot), in addition to that provided by SQL's isolation
levels. Actually, SQL prohibits insensitive scrollable cursors in
combination with update, although JDBC allows it, because some vendors
support it. Sensitive result sets makes changes made by other
transactions visible in the result set. If you just want the isolation
provided by SQL, you would want to use TYPE_SCROLL_SENSITIVE.

For Derby, we will probably want to build sensitive (first), to be SQL
compliant.

> updatable ResultSet
> -------------------
>
>          Key: DERBY-605
>          URL: http://issues.apache.org/jira/browse/DERBY-605
>      Project: Derby
>         Type: Improvement
>     Reporter: Veaceslav Chicu

>
> PreparedStatement st = conn.prepareStatement("select person_id, name, surname from tiers.person
for update",		
> ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
> ...
> rs.setObject(1, "aaa");
> rs.updateRow();
> needed for:
> I want a simple updatable table with gui (JTable , Table model work directly with ResultSet),
that scroll result set, and update it?
> simple table with 2.000.000 rows

-- 
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


Mime
View raw message