Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1683514
Title:
tests should ensure expand scripts don't have non-nullable columns
Status in neutron:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1683514/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp