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

Native user authentication: Docs do not describe what happens to schema and its SQL objects on SYSCS_UTIL.SYSCS_DROP_USER call

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.9.1.0
    • Fix Version/s: 10.9.1.0
    • Component/s: Documentation, Services
    • Labels:
      None

      Description

      Currently, the schema and the objects remain after the user is dropped, cf. repro2.sh attached.
      The authorization id of the schema of the dropped user is still that id (dangling) after DROP.
      Perhaps ownership should revert to the DBO when a user is dropped, or should DROP USER do a cascade delete?
      There is no way currently to change the ownership of the schema to another user.
      At the very least we should document what happens.

        Attachments

        1. DERBY-5747.diff
          0.9 kB
          Kim Haase
        2. repro2.sh
          0.7 kB
          Dag H. Wanvik
        3. rrefnativedropuserproc.html
          5 kB
          Kim Haase

          Issue Links

            Activity

              People

              • Assignee:
                chaase3 Kim Haase
                Reporter:
                dagw Dag H. Wanvik
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: