Details

      Description

      DERBY-5881 includes the following suggestion:

      3. The documentation for sized datatypes like char and varchar should be updated to warn about indexing limitations (which would most likely be encounterd with such datatypes).

      It probably also makes sense to add this recommendation to the introductory topic on indexes in the Tuning Guide (http://db.apache.org/derby/docs/dev/tuning/ctunperf10679.html).

      1. DERBY-5999-2.zip
        4 kB
        Kim Haase
      2. DERBY-5999-2.diff
        2 kB
        Kim Haase
      3. DERBY-5999.zip
        4 kB
        Kim Haase
      4. DERBY-5999.stat
        0.1 kB
        Kim Haase
      5. DERBY-5999.diff
        2 kB
        Kim Haase

        Activity

        Hide
        Kim Haase added a comment -

        Attaching DERBY-5999.diff, DERBY-5999.stat, and DERBY-5999.zip, with changes to two topics:

        M src/ref/rrefsqlj41207.dita
        M src/tuning/ctundepth1002853.dita

        There is no need, I think, to add a warning to the documentation of the CHAR data type. Since a CHAR can be no larger than 254 bytes, there is no danger of bumping into the page size limit.

        Please let me know if you have any suggestions for changes.

        Show
        Kim Haase added a comment - Attaching DERBY-5999 .diff, DERBY-5999 .stat, and DERBY-5999 .zip, with changes to two topics: M src/ref/rrefsqlj41207.dita M src/tuning/ctundepth1002853.dita There is no need, I think, to add a warning to the documentation of the CHAR data type. Since a CHAR can be no larger than 254 bytes, there is no danger of bumping into the page size limit. Please let me know if you have any suggestions for changes.
        Hide
        Knut Anders Hatlen added a comment -

        The patch looks like a good improvement. +1

        It is possible to bump into the page size limit with CHAR columns too, but then you'd need to have a multi-column index. I think it's OK not to mention that possibility in the documentation of the CHAR data type, though. What we already have documented in the CREATE INDEX topic is probably sufficient for CHAR and the other data types.

        Show
        Knut Anders Hatlen added a comment - The patch looks like a good improvement. +1 It is possible to bump into the page size limit with CHAR columns too, but then you'd need to have a multi-column index. I think it's OK not to mention that possibility in the documentation of the CHAR data type, though. What we already have documented in the CREATE INDEX topic is probably sufficient for CHAR and the other data types.
        Hide
        Kim Haase added a comment -

        Thanks, Knut, for the feedback!

        I discovered a syntax error in the Tuning Guide topic (involving paragraph tags) that for some reason didn't prevent the generation of correct output. I'm attaching a revised patch and zip, DERBY-5999-2.diff and DERBY-5999-2.zip. I'll commit the revised patch.

        Show
        Kim Haase added a comment - Thanks, Knut, for the feedback! I discovered a syntax error in the Tuning Guide topic (involving paragraph tags) that for some reason didn't prevent the generation of correct output. I'm attaching a revised patch and zip, DERBY-5999 -2.diff and DERBY-5999 -2.zip. I'll commit the revised patch.
        Hide
        Kim Haase added a comment -

        Committed patch DERBY-5999-2.diff to documentation trunk at revision 1412196.
        Merged to 10.9 doc branch at revision 1412279.
        Merged to 10.8 doc branch at revision 1412283.

        Show
        Kim Haase added a comment - Committed patch DERBY-5999 -2.diff to documentation trunk at revision 1412196. Merged to 10.9 doc branch at revision 1412279. Merged to 10.8 doc branch at revision 1412283.
        Hide
        Kim Haase added a comment -

        Closing, since the changes have appeared in the Latest Alpha Manuals.

        Show
        Kim Haase added a comment - Closing, since the changes have appeared in the Latest Alpha Manuals.

          People

          • Assignee:
            Kim Haase
            Reporter:
            Kim Haase
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development