I think the check constraint is automatically created by sqlalchemy to
enforce the Boolean type definition.
** Changed in: neutron (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Package changed: neutron (Ubuntu) => neutron-fwaas (Ubuntu)
** Changed in: neutron-fwaas
I think that if you rename a column the check constraint would need to
be dropped first and then re-created afterwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846606
Title:
[eoan] Unknown
Worth noting that mysql-8 is the first mysql release that supports check
constraints and they behave a little differently to pgsql ones.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846606
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: neutron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846606
Title:
