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
-
Similar issues:
KULRICE-5667Drop indexes and constraints in 2011-06-17-m6.sql may cause problems for users attempting to upgrade KULRICE-11061Build Labs page for inquiry features index KULRICE-11223Build Labs page for maintenance doc features index KULRICE-1944Add build number to index pages KULRICE-8985Add Index to prevent deadlocks during deletion of KSB entries KULRICE-12709 Add conditional constraint capability to data dictionary CollectionDefinition KULRICE-4803Add unique constraint on KIM permission namespace:name KULRICE-54Add referential integrity support to the OJB-to-DDL generator so that constraints can be added KULRICE-10103 Collection index on view only allows the same collection to be on the view once KULRICE-1438Add an index on workflow id, delegation type and doc hdr id to action item table ddl -
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.
Activity
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).
committed sql script and applied to dev db.
My tree was out of date, ignore me.
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
added note to 2.1m2-2.1m3 impacting changes doc
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.