Bug #39259 | Table entry field that should be NULL behaves improperly sometimes | ||
---|---|---|---|
Submitted: | 4 Sep 2008 21:44 | Modified: | 4 Oct 2008 22:26 |
Reporter: | David Zafman | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | Ver 14.12 Distrib 5.0.22 | OS: | Linux (CentOS release 5) |
Assigned to: | CPU Architecture: | Any | |
Tags: | DEFAULT, insert, null |
[4 Sep 2008 21:44]
David Zafman
[4 Sep 2008 21:45]
David Zafman
Session which shows database inconsistency
Attachment: bug39259.txt (text/plain), 7.54 KiB.
[4 Sep 2008 22:26]
MySQL Verification Team
Thank you for the bug report. Your server version is quite older (5.0.22) could you please try with latest released version 5.0.67. Thanks in advance.
[4 Oct 2008 23: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".