Details
Critical
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
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.
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.