[RFE] introduce explicit database constraint naming conventions

Bug #1660365 reported by milan k
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic Inspector
Triaged
Wishlist
Unassigned

Bug Description

Based on the discussion in the multi-attribute node look-up patch[1]

We didn't explicitly name database constraints before.
This leads to issues if we want to modify/drop constraints in a future schema update[2]

[1] https://review.openstack.org/#/c/421285/7/ironic_inspector/migrations/versions/882b2d84cb1b_attribute_constraints_relaxing.py@32
[2] http://docs.sqlalchemy.org/en/latest/core/constraints.html#configuring-constraint-naming-conventions

Tags: rfe
Anton Arefiev (aarefiev)
Changed in ironic-inspector:
importance: Undecided → Wishlist
tags: added: rfe
Changed in ironic-inspector:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.