Derby
  1. Derby
  2. DERBY-90

dblook displays message keys instead of their associated text

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.2.1
    • Fix Version/s: 10.0.2.1
    • Component/s: Tools
    • Labels:
      None

      Description

      Using Derby version 10.0.2.1 - (106978), when I execute
      java org.apache.derby.tools.dblook
      instead of getting the usage message, I get
      CSLOOK_Usage
      Similarly, when using dblook to generate database schema, the output text contains keys such as the one above, instead of their associated text. e.g.

      – CSLOOK_Timestamp, <2004-12-04 19:22:57.038>
      – CSLOOK_DBName, <sample>
      – CSLOOK_DBUrl, <jdbc:derby:sample>
      – appendLogs: false

      – ----------------------------------------------
      – CSLOOK_SchemasHeader
      – ----------------------------------------------

      CREATE SCHEMA "SAMP";

      – ----------------------------------------------
      – CSLOOK_TablesHeader
      – ----------------------------------------------

      CREATE TABLE "SAMP"."IN_TRAY" ("RECEIVED" TIMESTAMP, "SOURCE" CHAR(8), "SUBJECT" CHAR(64), "NOTE_TEXT" VARCHAR(3000));

        Activity

        Hide
        Ron Reuben added a comment -

        Army indicates that this has been fixed. I quote

        "I pointed this out to Andrew last week, and he checked in the fix with svn 109527"

        Since Derby's first release candidate contains this bug, it will need to be referenced in the "release notes". This is definitely not a "release-blocker" bug and should not affect the plans for release as long as end users are made aware of the issue.

        Show
        Ron Reuben added a comment - Army indicates that this has been fixed. I quote "I pointed this out to Andrew last week, and he checked in the fix with svn 109527" Since Derby's first release candidate contains this bug, it will need to be referenced in the "release notes". This is definitely not a "release-blocker" bug and should not affect the plans for release as long as end users are made aware of the issue.

          People

          • Assignee:
            A B
            Reporter:
            Ron Reuben
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development