Bug #39671 | INSERT INTO table gives PK violation but should not. | ||
---|---|---|---|
Submitted: | 26 Sep 2008 14:24 | Modified: | 23 Nov 2008 4:14 |
Reporter: | Oli Sennhauser | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 6.3.17 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[26 Sep 2008 14:24]
Oli Sennhauser
[26 Sep 2008 14:24]
Oli Sennhauser
config.ini
Attachment: config.ini (application/octet-stream, text), 1.67 KiB.
[26 Sep 2008 14:25]
Oli Sennhauser
my.cnf
Attachment: my.cnf (application/octet-stream, text), 296 bytes.
[23 Oct 2008 4:14]
Martin Skold
Did not manage to verify in latest 6.3 tree, please check if this is still a problem.
[31 Oct 2008 10:43]
Oli Sennhauser
I tried it with 6.3.18 but cannot reproduce. For me is fine to close now...
[31 Oct 2008 10:52]
Oli Sennhauser
Hi Martin I tried to verify with 6.3.18. But I could not. So for me it is solved! Oli
[24 Nov 2008 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[14 Oct 2010 21:25]
MySQL Verification Team
related to bug 57466 and that timestamp column??