Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-38783

Checks for explicit locks are unnecessary for ContentCollections

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.6.x
    • Fix Version/s: None
    • Component/s: Kernel
    • Labels:
    • Previous Issue Keys:
      KNL-255

      Description

      Calling CHS.allowUpdateCollection(id) or CHS.allowUpdateResource(id) (to see whether the current user can update a content entity) results in a call to checkExplicitLock(id). Locks are created using the RESOURCE_UUID, so checkExplicitLock(id) checks whether the entity has a RESOURCE_UUID and tries to assign one if it doesn't. Since ContentCollection's do not have RESOURCE_UUID's, this results in three meaningless SQL queries each time checkExplicitLock(id) is called.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                k1team KERNEL TEAM (Inactive)
                Reporter:
                jimeng Jim Eng (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Git Source Code