db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [jira] Updated: (DERBY-231) "FOR UPDATE" required for updatable result set to work
Date Thu, 03 Nov 2005 21:05:58 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Do you plan to make Derby client behave this way too? Currently Derby
client seems to match Embedded behavior if FOR UPDATE clause is not
specified and statement is ResultSet.CONCUR_UPDATABLE... With Derby
client, the cursor is <b>not </b>updatable in this case.<br>
<br>
Satheesh<br>
<br>
Andreas Korneliussen wrote:<br>
<blockquote cite="mid436A1825.2000708@sun.com" type="cite"><br>
There is no "setting to read only" as part of this patch, it is rather
the oposite.&nbsp; Today, the updatemode always defaults to read only if the
updateclause is unspecified. The change is simply to allow the cursor
to be UPDATABLE if the concurrency mode for the statement is
ResultSet.CONCUR_UPDATABLE.
  <br>
  <br>
-- Andreas
  <br>
</blockquote>
</body>
</html>


Mime
View raw message