Derby
  1. Derby
  2. DERBY-5004

Typo in column name "HASH_KEY_COLUMN_NUMBER" in SYSXPLAIN_SCAN_PROPS system table documentation

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.8.1.2
    • Component/s: Documentation
    • Labels:
      None

      Description

      ij> CONNECT 'jdbc:derby:myDb;create=false';
      ij> select HASH_KEY_COLUMN_NUMBER from (MY_SCHEMA.SYSXPLAIN_SCAN_PROPS NATURAL RIGHT OUTER JOIN MY_SCHEMA.SYSXPLAIN_RESULTSETS) where STMT_ID = 'a13ec033-012d-a987-d37e-000002c23230';
      ERROR 42X04: Column 'HASH_KEY_COLUMN_NUMBER' is either not in any table in the FROM list or appears within a join specification and is outside the scope of the join specification or appears in a HAVING clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE statement then 'HASH_KEY_COLUMN_NUMBER' is not a column in the target table.
      ij> select HASH_KEY_COLUMN_NUMBERS from (MY_SCHEMA.SYSXPLAIN_SCAN_PROPS NATURAL RIGHT OUTER JOIN MY_SCHEMA.SYSXPLAIN_RESULTSETS) where STMT_ID = 'a13ec033-012d-a987-d37e-000002c23230';
      HASH_KEY_COLUMN_NUMBERS
      --------------------------------------------------------------------------------------------------------------------------------
      NULL

      1 row selected
      ij>

      1. derby-5004.diff
        0.5 kB
        Nirmal Fernando

        Activity

        Hide
        Nirmal Fernando added a comment -

        Corrected the column name. Glad if someone can commit this!!

        Thanks!

        Show
        Nirmal Fernando added a comment - Corrected the column name. Glad if someone can commit this!! Thanks!
        Hide
        Dag H. Wanvik added a comment -

        Patch committed as svn 1067455. Thanks, Nirmal.

        As an aside, I noted that when searching for the string in the PDF version of the documents I didn't find it. Checking the table, I see that the columns in that format are too narrow, so only part of the identifier is shown: this affects the ability to search it too. Kim, have you noticed this? Do we have a way to fix it?

        Show
        Dag H. Wanvik added a comment - Patch committed as svn 1067455. Thanks, Nirmal. As an aside, I noted that when searching for the string in the PDF version of the documents I didn't find it. Checking the table, I see that the columns in that format are too narrow, so only part of the identifier is shown: this affects the ability to search it too. Kim, have you noticed this? Do we have a way to fix it?
        Hide
        Kim Haase added a comment -

        Thanks, Nirmal and Dag.

        Many tables in the documentation have columns whose text is unreadable in the PDF. The text column is narrow, but even using the full page width would not help in many cases. I don't know of any way to fix the problem (i.e. to make the text wrap within a word). The tables do look fine in the other two output formats.

        Show
        Kim Haase added a comment - Thanks, Nirmal and Dag. Many tables in the documentation have columns whose text is unreadable in the PDF. The text column is narrow, but even using the full page width would not help in many cases. I don't know of any way to fix the problem (i.e. to make the text wrap within a word). The tables do look fine in the other two output formats.
        Hide
        Knut Anders Hatlen added a comment -

        [bulk update] Close all resolved issues that haven't been updated for more than one year.

        Show
        Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.

          People

          • Assignee:
            Nirmal Fernando
            Reporter:
            Nirmal Fernando
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development