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

Regularize how we refer to object names in the Reference Manual

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.10.1.1
    • 10.10.2.0, 10.11.1.1
    • Documentation
    • None
    • Normal

    Description

      This issue came up during the buddy testing of user-defined aggregates. Here's what Dag discovered:

      identifiers (seen when looking at GRANT USAGE of aggregates): "table-Name" occurences are linked to a section explainig them (rreftablename.html), but UDA names are defined in-lined as

      GRANT USAGE ON DERBY AGGREGATE [ schemaName. ] SQL92Identifier TO grantees

      In a third variant,

      GRANT EXECUTE ON

      { FUNCTION | PROCEDURE }

      routine-designator TO grantees

      routine-designator is defined locally as

      routine-designator

      { function-name | procedure-name }

      without links to what "function-name" or "procedure-name" might look like. It would be good to harmonize the latter two forms to a central definition as for "table-Name".

      Finally, I noted that the definition page for SchemaName doesn't link to the SQL92Identifier page...

      Attachments

        1. rrefsqlj32268.html
          6 kB
          Camilla Haase
        2. DERBY-6121-3.zip
          7 kB
          Camilla Haase
        3. DERBY-6121-3.stat
          0.1 kB
          Camilla Haase
        4. DERBY-6121-3.diff
          3 kB
          Camilla Haase
        5. DERBY-6121-2.zip
          99 kB
          Camilla Haase
        6. DERBY-6121-2.stat
          2 kB
          Camilla Haase
        7. DERBY-6121-2.diff
          106 kB
          Camilla Haase
        8. DERBY-6121.zip
          249 kB
          Camilla Haase
        9. DERBY-6121.stat
          4 kB
          Camilla Haase
        10. DERBY-6121.diff
          242 kB
          Camilla Haase

        Issue Links

          Activity

            People

              chaase3 Camilla Haase
              rhillegas Richard N. Hillegas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: