Derby
  1. Derby
  2. DERBY-449

importing data using SYSCS_UTIL.SYSCS_IMPORT_DATA generates wrong message

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 10.0.2.1
    • Fix Version/s: None
    • Component/s: Tools
    • Labels:
      None
    • Environment:
      Solaris
    • Urgency:
      Low

      Description

      1. Launch ij to connect to Derby using embedded driver.
      2. Issue following command at ij prompt

      CALL SYSCS_UTIL.SYSCS_IMPORT_DATA(......);

      3. Even if several rows have been imported, at the end of import following message is given

      0 rows inserted/updated/deleted

      There are 2 issues:

      1. The message is misleading. Even if several rows got inserted with import, the message indicates 0.
      2. The message should not only indicate how many rows got imported successfully but also how many got rejected.

      This first problem seems to be only with embedded driver. Using Network Client driver to gives a more acceptable message "Statement executed".

        Issue Links

          Activity

          Hide
          Knut Anders Hatlen added a comment -

          Kathey suggested a while ago that we close this issue as Won't Fix. There were no objections, so I'm closing it now.

          I've linked the issue to DERBY-211 because the difference in the response from the client and the embedded driver is logged there.

          Show
          Knut Anders Hatlen added a comment - Kathey suggested a while ago that we close this issue as Won't Fix. There were no objections, so I'm closing it now. I've linked the issue to DERBY-211 because the difference in the response from the client and the embedded driver is logged there.
          Hide
          Mike Matrigali added a comment -

          Triaged July 10, 2009: assigned low urgency.

          Show
          Mike Matrigali added a comment - Triaged July 10, 2009: assigned low urgency.
          Hide
          Kathey Marsden added a comment -

          Unassigning due to inactivity. Please reassign yourself if you would like to work on this issue. Lowering priority. To ij this is just a stored procedure execution. I don't know how we could really improve the ij message.

          The next time I go through all the open issues (in a few months) I think I might close this Won't fix if nobody objects.

          Show
          Kathey Marsden added a comment - Unassigning due to inactivity. Please reassign yourself if you would like to work on this issue. Lowering priority. To ij this is just a stored procedure execution. I don't know how we could really improve the ij message. The next time I go through all the open issues (in a few months) I think I might close this Won't fix if nobody objects.

            People

            • Assignee:
              Unassigned
              Reporter:
              simmi iyer
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development