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

Duplicate indexes created on searchwriterlock

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.8.1
    • Fix Version/s: 10.0
    • Component/s: Search
    • Labels:
      None
    • Conversion Script Required:
      Yes
    • Previous Issue Keys:
      SRCH-78

      Description

      The search SQL and/or Hibernate HBM is creating two indexes on lockkey, only one of which is UNIQUE. There should be only one unique index created.

      CREATE TABLE `searchwriterlock` (
      `id` varchar(64) NOT NULL,
      `lockkey` varchar(64) NOT NULL,
      `nodename` varchar(64) DEFAULT NULL,
      `expires` datetime NOT NULL,
      PRIMARY KEY (`id`),
      UNIQUE KEY `lockkey` (`lockkey`),
      KEY `isearchwriterlock_lk` (`lockkey`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dhorwitz David Horwitz
                  Reporter:
                  smarquard Stephen Marquard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code