[jira] Created: (DERBY-154) Does Network Server support scroll sensitive read-only and updatable resultsets?

Does Network Server support scroll sensitive read-only and updatable resultsets?
--------------------------------------------------------------------------------

         Key: DERBY-154
         URL: http://issues.apache.org/jira/browse/DERBY-154
     Project: Derby
        Type: Bug
  Components: Network Server  
    Versions: 10.0.2.1    
    Reporter: Mamta A. Satoor


Derby in embedded mode does not support scroll sensitive resultsets in both 
read-only and updatable modes. But when I write a simple test program in 
Network Server configuration, it appears that scroll sensitive resultsets are 
supported both in read-only and updatable modes. Is that correct?

Connection con = 
DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true:deferPrepares=false;",
 "app", "app");
Statement s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, 
ResultSet.CONCUR_READ_ONLY);
SQLWarning warnings = con.getWarnings();
while (warnings != null)
{
        System.out.println("warnings on connection = " + warnings);
        warnings = warnings.getNextWarning();
}
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " +  
(s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_READ_ONLY? " +  
(s.getResultSetConcurrency() == ResultSet.CONCUR_READ_ONLY));

s = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, 
ResultSet.CONCUR_UPDATABLE);
System.out.println("Did we get TYPE_SCROLL_SENSITIVE? " +  
(s.getResultSetType() == ResultSet.TYPE_SCROLL_SENSITIVE));
System.out.println("Did we get CONCUR_UPDATABLE? " +  
(s.getResultSetConcurrency() == ResultSet.CONCUR_UPDATABLE));

And the output in Network Server mode for above test case is
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_READ_ONLY? true
Did we get TYPE_SCROLL_SENSITIVE? true
Did we get CONCUR_UPDATABLE? true


-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira