db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-154) Network Client should not allow creation of statements with scroll sensitive read-only and updatable resultsets?
Date Tue, 14 Jul 2009 22:05:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731156#action_12731156
] 

Myrna van Lunteren commented on DERBY-154:
------------------------------------------

[10.5.2 Triage]
I made a repro using the Derby Net client instead of the JCC driver 
(         Connection con = DriverManager.getConnection("jdbc:derby://localhost:1527/db1drda;create=true;");)
and got the following output:

Did we get TYPE_SCROLL_SENSITIVE? false
Did we get CONCUR_READ_ONLY? true
Did we get TYPE_SCROLL_SENSITIVE? false
Did we get CONCUR_UPDATABLE? true

The output for embedded is exactly the same. 
As we no longer cater towards the JCC driver, I don't think there's anything more to do here.



> Network Client should not allow creation of statements with  scroll sensitive read-only
and updatable resultsets?
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-154
>                 URL: https://issues.apache.org/jira/browse/DERBY-154
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message