[ http://issues.apache.org/jira/browse/DERBY-965?page=all ]
Dag H. Wanvik updated DERBY-965:
--------------------------------
Attachment: derby965-v3.stat
derby965-v3.diff
This patch updates the master for phaseTester.java . This test is not part
of derbyall and the master must be manually compared
with the output of the phase tests, cf description in DERBY-573.
phaseTester runs metadata_test.java as part of its work, so the master needs to
be updated
whenever metadata_test.java changes (as this issue does).
Note: Even with this patch, phaseTester when run as described, failed. I
noticed the following:
- the shell script driving it is WIndows specific (";" as classpath delimiter)
- in the soft upgrade phase, the metadata test fails (table not found), when
performing a stored
procedure: 'CALL SYSIBM.SQLCOLPRIVILEGES' (in odbc_metadata#getMetadataRS).
This patch lessens the diff between the master and the "current" output,
though, so i think
it should be committed.
> DatabaseMetadata method supportsResultSetConcurrency returns wrong result on
> network client
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-965
> URL: http://issues.apache.org/jira/browse/DERBY-965
> Project: Derby
> Type: Bug
> Components: Network Server, Network Client
> Versions: 10.2.0.0
> Environment: Solaris 10, x86, Sun JDK 1.4.2
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: Main.java, derby965-v1.diff, derby965-v1.stat,
> derby965-v2.diff, derby965-v2.stat, derby965-v3.diff, derby965-v3.stat
>
> The DatabaseMetaData method supportsResultSetConcurrency erroneously
> returns false on the network client for all arguments combination, cf
> the attached repro program. The embedded client returns correct
> results, viz the output:
> org.apache.derby.jdbc.ClientDriver:
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_UPDATABLE: false
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_UPDATABLE: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_UPDATABLE: false
> org.apache.derby.jdbc.EmbeddedDriver:
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_READ_ONLY: true
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_UPDATABLE: true
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_READ_ONLY: true
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_UPDATABLE: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_UPDATABLE: false
> Presumably, this is wrong in released versions as well.
--
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
