No default value and not null, should mean failure on alter table
Bug #686197 reported by
Brian Aker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Medium
|
Brian Aker | ||
| 7.0 |
Fix Released
|
Medium
|
Brian Aker | ||
Bug Description
We inherited this from MySQL. If you alter table and add a field which is NOT NULL and has no default value, the alter table should fail because there is no valid data to insert into the field.
| Changed in drizzle: | |
| assignee: | nobody → Brian Aker (brianaker) |
To post a comment you must log in.
