logilab-database #167781 drop_multicol_unique_index should not fail if the index does not exist in the database. [validation pending]
The method should not fail if the index does not exist. We want this in order to avoid, "under-the-hood" rollbacks in CubicWeb; see this ticket. | |
| priority | normal |
|---|---|
| type | bug |
| done in | 1.13.4 |
| load | 2.000 |
| load left | 0.000 |
| closed by | #65e98f57d604 Drop indexes only if they exist (closes #167781). |
| patch | [sqlserver] Drop unique index only if it exists [folded][generic] Drop indexes only if they exist (closes #167781). [applied][generic, sqlserver] Drop multicolumn unique indexes only if they exist (closes #167781). [folded] |
Comments
-
2015/06/27 12:34, written by acampeas
-
2015/06/29 16:03, written by jcristau
-
2015/06/29 16:27, written by acampeas
add commentJulien, can you move it to the next version ? (permission issue for me).
this is done, but please explain why this is something we want.
The patch set which resets utcs around rdefs needs this. Some operations, while being data operations, are nonetheless consumed several times within one transaction. Hence we must prevent double removals of the contraints.