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: DerbyNetClient/lang/updatableResultSet fails
Date Thu, 02 Jun 2005 20:39:23 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
I was trying to update some other master outputs, following Tomohito's
change. Looks like this got changed along with others. I can either
revert this or if it has already been done, then ok.<br>
Mamta Satoor wrote:<br>
<blockquote cite="midd9619e4a05060213234ad099d@mail.gmail.com"
  <div>I am trying to understand the reasons behind
updatableResultset&nbsp;test&nbsp;failure when using DerbyNetClient. Following is
what I have found so far.</div>
  <div>Satheesh made a checkin on May 25th (revision 178519) to the
master file DerbyNetClient/updatableResultSet.out which was as follows</div>
Wed May 25 12:39:51 2005<br>
@@ -307,14 +307,14 @@<br>
&nbsp;delete using first resultset<br>
&nbsp;attempt to send deleteRow on the same row through a different
resultset should throw an exception
&nbsp;SQL State : XCL08<br>
-Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.<br>
+Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.<br>
&nbsp;Move to next row in the 2nd resultset and then delete using the second
&nbsp;Positive Test11 - setting the fetch size to &gt; 1 will be ignored by
updatable resultset. Same as updatable cursors<br>
&nbsp;Notice the Fetch Size in run time statistics output.<br>
&nbsp;Statement Name:<br>
- &nbsp; &nbsp; &nbsp; SQL_CURLH000C54
+ &nbsp; &nbsp; &nbsp; SQL_CURLH000C55<br>
&nbsp;Statement Text:<br>
&nbsp; &nbsp; &nbsp; &nbsp;SELECT * FROM t1 FOR UPDATE of c1<br>
&nbsp;Parse Time: 0<br>
On May 26th, Bernt reported a diff which is reverse of master update
done by Satheesh.&nbsp;Checkin from today (revision 179592) submitted by
David seems to bring the master back to the state prior to Satheesh's
  <div>Also, Bernt, I looked at <a
 onclick="return top.js.OpenExtLink(window,event,this)"
  </a>&nbsp;and the reason you didn't see the failure on Linux 2.4.19 and
jdk1.4.2_08 I think is because the test never got run on that machine
for some reason. In the list of tests that ran as part of
derbynetclientmats on Linux 2.4.19 and jdk1.4.2_08, I don't see
updatableResultset test in there.&nbsp;Let me know if I have missed
anything. But if I am right, then we don't need <font color="#550055">updatableResultSet_sed.properties
since&nbsp;we&nbsp;should get same&nbsp;cursor name irrespective&nbsp;of different
  <div><font color="#550055">The only question I have is why did
Satheesh need to change the master? I am running with classes and maybe
there is something that shows up only with the jar files. Satheesh,
please let me know if there is an environment that I have not tested
which required the master update.
  <div><font color="#550055">thanks,</font></div>
  <div><font color="#550055">Mamta</font><br>
  <pre><span class="gmail_quote">On 5/26/05, <b class="gmail_sendername">Bernt
M. Johnsen</b> &lt;<a
 href="mailto:Bernt.Johnsen@sun.com">Bernt.Johnsen@sun.com</a>&gt; wrote:
</span> </pre>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left:
running derbyall, DerbyNetClient/lang/updatableResultSet fails<br>
the following way:<br>
*** Start: updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26
23:12:55 ***<br>
Initialize for framework: DerbyNetClient<br>
java -ms16777216 -mx33554432
byNetClient/updatableResultSet -Djava.security.manager
-Djava.security.policy=/e xport/home/tmp/Derby/test/nwsvr.policy
-Dcsinfo.codebase=/export/home/tmp/Derby/ trunk/jars/sane
-Dcsinfo.serverhost=localhost -Dcsinfo.trustedhost=localhost org
.apache.derby.drda.NetworkServerControl start
Attempt to shutdown framework: DerbyNetClient<br>
310 del<br>
&lt; Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.<br>
&gt; Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.<br>
317 del<br>
&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SQL_CURLH000C55<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SQL_CURLH000C54<br>
Test Failed.<br>
*** End:&nbsp;&nbsp; updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26
23:13:22 ***<br>
(Same error with 1.5 and 1.3)<br>
I'm running with Linux 2.6.11. What I find strange, is that when I<br>
inspect the test failures in<br>
I see that the same test fails in the same way on all platforms,<br>
with the exception of the test run on a Linux 2.4.19 and jdk1.4.2_08<br>
Comment anynone?<br>
Bernt Marius Johnsen, Database Technology Group,
Sun Microsystems, Trondheim, Norway<br>

View raw message