My vote is for the intermediate table to store the MAC address and enforce unique constraint on the mac address field. No need of extra triggers when it can be solved in a simple way and no need to add extra code to handle it. On Tue, Oct 20, 2015 at 5:08 AM, William Stevenson <yhvh2000 at gmail.com> wrote: > Hi, > > In reference to comments on a patchset[1], port/portgroup addresses > should be unique. Please also see the irc log[1] which includes > earlier discussion regarding rationale. > > Q: How can we enforce this uniqueness across tables? > > > [1] > https://review.openstack.org/#/c/206232/26/ironic/db/sqlalchemy/alembic/versions/5ea1b0d310e_added_port_group_table_and_altered_ports.py > [2] http://ix.io/luF/irc > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151102/d5007021/attachment.html>