Constraint Status - repeats

[Paolo F Cantoni]

I was leafing through Settings | Project Types [ch9658] | General Types… when I chanced upon the Constraint Status tab.

The values shown in there were the 6 expected types - but each one was repeated 5 times!

Anyone else see this (before I report the bug).

TIA,
Paolo

[qwerty]

Mine are okay. But instead of reporting a bug simply delete the duplicates. Heaven knows how they got there.

q.

[Paolo F Cantoni]

Mine are okay. But instead of reporting a bug simply delete the duplicates. Heaven knows how they got there.

q.

I thought they weren't duplicated in the DB

But it seems I wasn't pointing at the right DB...  

However, one interesting side effect is that if I delete using the EA UI - although I delete 1 entry, ALL the entries with that value are deleted!

More EAUI!

Paolo

[Geert Bellekens]

Hmm, I can perfectly imagine how that came about:

Problem: implement delete button
Solution: Delete from <contraint table> where name = '<selectedConstraint.name>'

Geert

[Paolo F Cantoni]

Hmm, I can perfectly imagine how that came about:

Problem: implement delete button
Solution: Delete from <constraint table> where name = '<selected Constraint.name>'

Geert

Wrong use case!  

Problem: implement delete button for selected constraint only

Since name is NOT unique, you shouldn't delete on it...

Paolo

[stevesavage]

@Paulo, you might get multiple copies of constraints if someone has merged the "reference data" from multiple repositories in to a single repository.  I had something similar happen recently when I was merging two repositories in to a single repository.

[Paolo F Cantoni]

@Paulo, you might get multiple copies of constraints if someone has merged the "reference data" from multiple repositories in to a single repository.  I had something similar happen recently when I was merging two repositories in to a single repository.

Understood...  My point is that since name is not unique you shouldn't delete on it.  You run the risk of deleting ALL the instances, including the ONE you wanted to keep.

In my work in the background - direct to the database - I often generate duplicate things during development and testing so I have a standard technique for removing the extra duplicates and (unfortunately) it needs to rely on an external table to hold the candidates for purging.

Paolo