Derby
  1. Derby
  2. DERBY-5900

Need to correct Reference Guide description of contents of SYS.SYSPERMS.OBJECTTYPE

    Details

    • Urgency:
      Normal

      Description

      The Reference Guide section on SYS.SYSPERMS says that the OBJECTTYPE column can take the following values:

      'SEQUENCE' and 'USER-DEFINED TYPE'

      This is not correct. The legal values are:

      'SEQUENCE' and 'TYPE'

      1. DERBY-5900.diff
        0.5 kB
        Kim Haase
      2. rrefsistabssysperms.html
        7 kB
        Kim Haase

        Activity

        Rick Hillegas created issue -
        Kim Haase made changes -
        Field Original Value New Value
        Assignee Kim Haase [ chaase3 ]
        Hide
        Kim Haase added a comment -

        Thanks for catching this problem, Rick. Attaching DERBY-5900.diff and rrefsistabssysperms.html, with the fix to rrefsistabssysperms.dita. Please let me know if any changes are needed.

        Show
        Kim Haase added a comment - Thanks for catching this problem, Rick. Attaching DERBY-5900 .diff and rrefsistabssysperms.html, with the fix to rrefsistabssysperms.dita. Please let me know if any changes are needed.
        Kim Haase made changes -
        Attachment DERBY-5900.diff [ 12540661 ]
        Attachment rrefsistabssysperms.html [ 12540662 ]
        Kim Haase made changes -
        Issue & fix info Patch Available [ 10102 ]
        Hide
        Kim Haase added a comment -

        Looks as if this fix should be backported to 10.9 as well as fixing it in the trunk – right?

        Show
        Kim Haase added a comment - Looks as if this fix should be backported to 10.9 as well as fixing it in the trunk – right?
        Hide
        Rick Hillegas added a comment -

        Thanks for the quick fix, Kim. +1

        It wouldn't hurt to backport the fix all the way to 10.6, the release which introduced user defined types. Thanks.

        Show
        Rick Hillegas added a comment - Thanks for the quick fix, Kim. +1 It wouldn't hurt to backport the fix all the way to 10.6, the release which introduced user defined types. Thanks.
        Hide
        Kim Haase added a comment -

        Sure – thanks, Rick.

        Committed patch DERBY-5900.diff to documentation trunk at revision 1372463.
        Merged to 10.9 doc branch at revision 1372469.
        Merged to 10.8 doc branch at revision 1372479.

        Because of some formatting fixes introduced in 10.8, merging to 10.7 (or earlier) results in a conflict:

        jdench 86 =>svn merge --dry-run -r 1372462:1372463 https://svn.apache.org/repos/asf/db/derby/docs/trunk/
        — Merging r1372463 into '.':
        C src/ref/rrefsistabssysperms.dita
        Summary of conflicts:
        Text conflicts: 1

        The reason is that the patch is from one line with <i> tags to another –

        -values are <i>'SEQUENCE'</i> and <i>'USER-DEFINED TYPE'</i>.</entry>
        +values are <i>'SEQUENCE'</i> and <i>'TYPE'</i>.</entry>

        but in 10.7/10.6 there are no <i> tags:

        values are 'SEQUENCE' and 'USER-DEFINED TYPE'.</entry>

        Should I just make the changes in these two branches and commit them without merging, or is there a merge command option that would get around this?

        Show
        Kim Haase added a comment - Sure – thanks, Rick. Committed patch DERBY-5900 .diff to documentation trunk at revision 1372463. Merged to 10.9 doc branch at revision 1372469. Merged to 10.8 doc branch at revision 1372479. Because of some formatting fixes introduced in 10.8, merging to 10.7 (or earlier) results in a conflict: jdench 86 =>svn merge --dry-run -r 1372462:1372463 https://svn.apache.org/repos/asf/db/derby/docs/trunk/ — Merging r1372463 into '.': C src/ref/rrefsistabssysperms.dita Summary of conflicts: Text conflicts: 1 The reason is that the patch is from one line with <i> tags to another – -values are <i>'SEQUENCE'</i> and <i>'USER-DEFINED TYPE'</i>.</entry> +values are <i>'SEQUENCE'</i> and <i>'TYPE'</i>.</entry> but in 10.7/10.6 there are no <i> tags: values are 'SEQUENCE' and 'USER-DEFINED TYPE'.</entry> Should I just make the changes in these two branches and commit them without merging, or is there a merge command option that would get around this?
        Hide
        Rick Hillegas added a comment -

        Hi Kim,

        I don't know a fancy way to handle this conflict. This is what I do in these situations:

        o svn merge the original patch into your client on the older branch

        o hand-correct the problems

        o then svn resolve the files so that subversion understands that the merge is complete

        o commit the result to the older branch

        Thanks,
        -Rick

        Show
        Rick Hillegas added a comment - Hi Kim, I don't know a fancy way to handle this conflict. This is what I do in these situations: o svn merge the original patch into your client on the older branch o hand-correct the problems o then svn resolve the files so that subversion understands that the merge is complete o commit the result to the older branch Thanks, -Rick
        Hide
        Kim Haase added a comment -

        Thanks again, Rick.

        I did something that seems to work though it's not exactly what you did: when I ran the svn merge without the --dry-run switch, I took the "mc" (mine-conflict) option, which left the file as it was; I then made the one needed edit, which left the status as "M".

        Committed to 10.7 doc branch at revision 1372533.
        Committed to 10.6 doc branch at revision 1372542.

        Show
        Kim Haase added a comment - Thanks again, Rick. I did something that seems to work though it's not exactly what you did: when I ran the svn merge without the --dry-run switch, I took the "mc" (mine-conflict) option, which left the file as it was; I then made the one needed edit, which left the status as "M". Committed to 10.7 doc branch at revision 1372533. Committed to 10.6 doc branch at revision 1372542.
        Kim Haase made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Issue & fix info Patch Available [ 10102 ]
        Fix Version/s 10.6.2.2 [ 12315370 ]
        Fix Version/s 10.7.1.4 [ 12315902 ]
        Fix Version/s 10.8.2.3 [ 12318540 ]
        Fix Version/s 10.9.1.1 [ 12321551 ]
        Fix Version/s 10.10.0.0 [ 12321550 ]
        Resolution Fixed [ 1 ]
        Hide
        Kim Haase added a comment -

        Correction has appeared in latest Alpha manuals as well as recently regenerated 10.9 and 10.8 manuals.

        Show
        Kim Haase added a comment - Correction has appeared in latest Alpha manuals as well as recently regenerated 10.9 and 10.8 manuals.
        Kim Haase made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Kathey Marsden made changes -
        Fix Version/s 10.8.3.0 [ 12323456 ]
        Fix Version/s 10.8.2.3 [ 12318540 ]
        Kathey Marsden made changes -
        Fix Version/s 10.9.2.0 [ 12323562 ]
        Fix Version/s 10.9.1.1 [ 12321551 ]
        Gavin made changes -
        Workflow jira [ 12721050 ] Default workflow, editable Closed status [ 12801742 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development