| Ticket Hash: | 719070231d595cbca0c469523cbfd11477b1d4e2 | ||
| Title: | Constraint conflict resolution method not read into database designer | ||
| Status: | Closed | Type: | Code_Defect |
| Severity: | Severe | Priority: | Immediate |
| Subsystem: | VsDesigner | Resolution: | Duplicate |
| Last Modified: |
2011-07-07 04:55:24 14.00 years ago |
Created: |
2011-04-18 13:11:10 14.22 years ago |
| Version Found In: | 1.0.66.0 | ||
| Description: | ||||
|
Certainly with PK unique constraint resolution method, perhaps with others, "ON CONFLICT IGNORE" is saved, but then not read back in to the database designer on later visits. Therefore, re-visits do not reflect changes made previously and list the method to apply as the default ABORT.
More severely, any further saves of the table design cause the default method to be applied in error. shane added on 2011-04-19 12:37:46 UTC: | ||||