Bug #34468 main.csv_not_null test failing
Submitted: 11 Feb 2008 16:53 Modified: 25 Feb 2008 17:52
Reporter: Patrick Crews Email Updates:
Status: Closed Impact on me:
None 
Category:Tests: Engine Severity:S3 (Non-critical)
Version:5.1, 6.0 OS:Any
Assigned to: Patrick Crews CPU Architecture:Any
Tags: csv, Tests, UPDATE statements
Triage: D3 (Medium)

[11 Feb 2008 16:53] Patrick Crews
Description:
test csv_not_null has begun to fail.

This is due to a change in UPDATE statements.  Previously, UPDATE set <non-nullable-column> = NULL WHERE <condition> would be allowed in non-strict mode, resulting in the column being set to the datatype default value.

This behavior has since been changed and such statements now throw an error - 1048 - ER_BAD_NULL_ERROR

How to repeat:
From the mysql-test directory run ./mysql-test-run csv_not_null

You will see a failure as a result of a statement that uses an UPDATE statement from the description

Suggested fix:
Re-record the .result file for csv_not_null after altering the test to expect a 
ER_BAD_NULL_ERROR error.
[25 Feb 2008 15:58] Bugs System
Pushed into 5.1.24-rc
[25 Feb 2008 16:04] Bugs System
Pushed into 6.0.5-alpha
[25 Feb 2008 17:52] Paul Dubois
Test case change. No changelog entry needed.