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

CLOB INOUT arg set to NULL by procedure does not preserve NULL value when re-invoked

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.8.1.2
    • 10.8.1.2
    • JDBC, SQL
    • None
    • Repro attached
    • Wrong query result

    Description

      If a procedure sets an INOUT CLOB arg to NULL and is then re-invoked, the NULL is not preserved. Instead, the procedure sees the same CLOB that it saw in the last invocation. This bug was disclosed during the testing of the fix for DERBY-2515. I will attach a repro.

      Attachments

        1. z.java
          6 kB
          Richard N. Hillegas
        2. derby-5162-01-aa-restoreToNull.diff
          0.4 kB
          Richard N. Hillegas

        Issue Links

        is depended upon by

        Bug - A problem which impairs or prevents the functions of the product. DERBY-2515 Network client does not retain the INOUT parameter value change for subsequent execution

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

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

          People

            rhillegas Richard N. Hillegas
            rhillegas Richard N. Hillegas
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment