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
I have a table entry which produces inconsistent results.  It is supposed to be NULL because an INSERT from perl was done which did NOT mention the "mac" field and there is no DEFAULT set.  Also, the field is not set "NOT NULL".

I've seen this a few times, but most of the time the same insert creates a normal db entry.  I show an example of INSERT of another entry in the same table below.  The second entry works fine, so I presume the whole table isn't in a bad state.  A restart of the mysql daemon did NOT make the problem go away.

I will attach a session which shows the db inconsistency.

How to repeat:
Intermittent problem occurs sometime on INSERT see above.  I can't provide an exact step(s) to reliably reproduce.

Suggested fix:
[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] Miguel Solorzano
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".