#31 Missing Unique Constraints

[chris gilbert]

There are several places in WAF and CMS where the
absence of unique attributes causes inconsistent
state - usually this can only be fixed directly in
the database.

eg - folders. When the first item in a folder is
published, a live folder is created, but if two items
are concurrently published then 2 live folders are
created by the separate transactions and from that
point, no items in the folder may be viewed as the
assertion that folders cannot contain items with the
same name is broken (the parent folder contains the 2
live folders)

eg - party primary emails. When creating users, a
double click on submit can create 2 parties with the
same primary email. The user cannot login because of
an assertion failure.

I suspect there are several places where unique
attributes should be specified in pdl. Including
these may cause some users to get unexpected errors
when their transactions are thrown out of the
database but that is better than arriving at
inconsistent state that cannot be corrected through
the ui.

Chris.....