tests should ensure expand scripts don't have non-nullable columns

Bug #1683514 reported by Kevin Benton on 2017-04-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Low
Unassigned

Bug Description

Currently our tests don't prevent us from adding a non-nullable column without a server default. This will prevent older versions of the server from inserting records into the table so we can't let these merge.

It would be good if we had a test in our migration validation logic that ensures that any added columns are either nullable or they define a server-default.

tags: added: db
Changed in neutron:
importance: Undecided → Low
status: New → Confirmed
tags: added: low-hanging-fruit
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers