Timeline for Add UNIQUE index fails with duplicate entry error, but no duplicates found
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Apr 9, 2020 at 11:03 | history | suggested | robsch | CC BY-SA 4.0 |
removed german word
|
Nov 19, 2019 at 10:46 | review | Suggested edits | |||
S Apr 9, 2020 at 11:03 | |||||
May 11, 2019 at 18:24 | comment | added | Afgan | How did you find real "duplicate value" . I am also running in this issue, can please help me out to debug issue further | |
Jul 22, 2016 at 22:11 | comment | added | Peter | I agree with kromit. I have updated a table, setting UNIQUE to a field and the error message was wrong (indicating a value which was not duplicated). I was able to find the real "duplicate value" and they were not the one of the message. | |
Aug 18, 2015 at 21:05 | vote | accept | Roman K | ||
Jul 9, 2015 at 6:20 | comment | added | Roman K | Because the returned combination exist only once. I guess its just a message bug. Evtl. the left or right neighbor is the real duplicate entry. | |
Jul 8, 2015 at 11:37 | comment | added | ypercubeᵀᴹ | How did you conclude that there is no guarantee? | |
Jul 8, 2015 at 11:26 | comment | added | Roman K | Sorry, I've tried this with 500k but without success. Seems to be something in >1 Mio area. | |
Jul 8, 2015 at 11:05 | comment | added | jkavalik | Could you make it into a test case with few to few thousands of rows which reproduces this? | |
Jul 8, 2015 at 11:00 | history | answered | Roman K | CC BY-SA 3.0 |