On Mon, Sep 21, 2015 at 12:28:35 -0700, Quanah Gibson-Mount wrote:

The rationale was that manageDSAit means let me operate on the raw data and disable all side-effects. This is still correct and should remain.

For clarity I do agree that a control should exist to bypass uniqueness (and other) constraints. However I think manageDSAit is not the appropriate control by its definition, and also in practice given the fact it's set per default by popular client libs.

Relax Rules seems much more appropriate for this use case, as it's intended to temporarily relax database constraints, for administrative use only.

However, an option could be added to the module to disable this control specifically for this overlay.

No, then I would need to change the server config to disable that option each time I'd wish to temporarily bypass the constraint, instead of using another dedicated control for that (which would need no disable option).

Geert