Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-173

For the concurrency of ResultSet, Network Server should not send the concurrency of Statement.

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.0.2.1
    • 10.1.1.0
    • Network Server
    • None

    Description

      I am working on getting updatable resulset functionality to work under Network Server. One issue that I found is Network Server sends the concurrency of the Statement object when it really needs to send the concurrency of the Resultset. This was ok in the past because CONCUR_READ_ONLY was the only concurreny supported by Derby. But, now with the support of CONCUR_UPDATABLE, it is possible that the concurrency of ResultSet might not be same as the Statement object. Hence, Network Server should send the concurrency of the ResultSet object if that is what the protocol calls for.

      The fix for this is localized in java\drda\org\apache\derby\impl\drda\DRDAConnThread.java.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mamtas Mamta A. Satoor
            mamtas Mamta A. Satoor
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment