Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-6784

Add index and constraint on KREW_RULE_ATTR_T.NM

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Complete
    • Affects Version/s: 2.0
    • Fix Version/s: 2.1
    • Component/s: Database
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      we should add an index and unique constraint to the NM field on KREW_RULE_ATTR_T table. The code assumes that NAME is unique, but the database doesn't represent that. Also, we have service calls that grab data from this table on the NM alone, so we should have an index on that field.

        Attachments

          Activity

          Hide
          ewestfal Eric Westfall added a comment -

          One thing to note here, I think that if you add a uniqueness constraint to a column you don't need to also index it. But I could be wrong on that. Whoever gets this issue should check on whether or not we need both a uniqueness constraint and an index or just a uniqueness constraint.

          Show
          ewestfal Eric Westfall added a comment - One thing to note here, I think that if you add a uniqueness constraint to a column you don't need to also index it. But I could be wrong on that. Whoever gets this issue should check on whether or not we need both a uniqueness constraint and an index or just a uniqueness constraint.
          Hide
          ahamid Aaron Hamid (Inactive) added a comment -

          Apparently in MySQL (5.5.20) a unique constraint creates (is equivalent to) an index.
          While docs seem to vary on this, testing reveals that adding a constraint in Oracle (11.1.0.0.0) also results in an index (an error is produced if an attempt is made to introduce an additional index afterwards).

          Show
          ahamid Aaron Hamid (Inactive) added a comment - Apparently in MySQL (5.5.20) a unique constraint creates (is equivalent to) an index. While docs seem to vary on this, testing reveals that adding a constraint in Oracle (11.1.0.0.0) also results in an index (an error is produced if an attempt is made to introduce an additional index afterwards).
          Hide
          ahamid Aaron Hamid (Inactive) added a comment -

          committed sql script and applied to dev db.

          Show
          ahamid Aaron Hamid (Inactive) added a comment - committed sql script and applied to dev db.
          Hide
          gilesp Peter Giles (Inactive) added a comment - - edited

          My tree was out of date, ignore me.

          Show
          gilesp Peter Giles (Inactive) added a comment - - edited My tree was out of date, ignore me.
          Hide
          gilesp Peter Giles (Inactive) added a comment -

          This isn't strictly speaking an impacting change, but I think we should probably add all DB changes to https://wiki.kuali.org/display/KULRICE/Post-2.0+impacting+changes

          Show
          gilesp Peter Giles (Inactive) added a comment - This isn't strictly speaking an impacting change, but I think we should probably add all DB changes to https://wiki.kuali.org/display/KULRICE/Post-2.0+impacting+changes
          Hide
          ahamid Aaron Hamid (Inactive) added a comment -

          added note to 2.1m2-2.1m3 impacting changes doc

          Show
          ahamid Aaron Hamid (Inactive) added a comment - added note to 2.1m2-2.1m3 impacting changes doc

            People

            • Assignee:
              ahamid Aaron Hamid (Inactive)
              Reporter:
              jjhanso Jeremy Hanson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: