You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Manjula Kutty (JIRA)" <ji...@apache.org> on 2007/02/09 19:38:06 UTC
[jira] Updated: (DERBY-2317) Difference in the cursor.getcursorName
behaviour between n/w server and embedded mode, where embedded retuns null
and n/w server returns the cursor name
[ https://issues.apache.org/jira/browse/DERBY-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjula Kutty updated DERBY-2317:
---------------------------------
Fix Version/s: (was: 10.3.0.0)
Summary: Difference in the cursor.getcursorName behaviour between n/w server and embedded mode, where embedded retuns null and n/w server returns the cursor name (was: Difference in the cursor.getcursorName behaviour between n/w server and embedded mode)
> Difference in the cursor.getcursorName behaviour between n/w server and embedded mode, where embedded retuns null and n/w server returns the cursor name
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2317
> URL: https://issues.apache.org/jira/browse/DERBY-2317
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.3.0.0
> Reporter: Manjula Kutty
> Attachments: TestCursor.java
>
>
> Please find the attached small java test which gives you the different behaviour. Please find the following mail thread which says the embedded mode's behaviour is correct.
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200702.mbox/%3cwjo8r6sz8zku.fsf@sun.com%3e
> To run the test in the embedded mode
> java TestCursor embedded
>
> in n/w server ( have to start the server seperately)
>
> java TestCursor NetworkServer
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.