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

Behaviour of setTypeMap() differs between embedded and client

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

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 10.5.1.1
    • 10.6.1.0
    • JDBC
    • None
    • Newcomer
    • Embedded/Client difference

    Description

      On the embedded driver, Connection.setTypeMap() behaves like this (when the connection is not closed):

      • if the map argument is null, throw an SQLException with SQLState XJ081
      • if the map is not null and not empty, throw an SQLException with SQLState 0A000
      • if the map is not null and empty, do nothing

      The behaviour on the client driver is this:

      • always throw an SQLException with SQLState 0A000

      We should try to make the two drivers behave the same way when setTypeMap() is called. (This would also allow us to simplify some of the tests in J2EEDataSourceTest).

      Attachments

        1. DERBY-3853-1.patch
          3 kB
          Yun Lee
        2. DERBY-3853-1.stat
          0.2 kB
          Yun Lee
        3. DERBY-3853-2.patch
          15 kB
          Yun Lee
        4. DERBY-3853-2.stat
          0.2 kB
          Yun Lee
        5. releaseNote.html
          4 kB
          Knut Anders Hatlen

        Issue Links

        Activity

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

          People

            yunlee Yun Lee
            knutanders Knut Anders Hatlen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment