Oracle should have a parameter, settable at the session level especially for testing,
that triggers an error any time the session executes SQL with a many-to-many join!
More-sophisticated uniqueness constraints (for example, uniqueness of a column
combination just for a particular subset of a table) would help, here.