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