You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2019/09/04 16:32:12 UTC

[GitHub] [trafficcontrol] rawlinp commented on issue #3893: Add a database constraint preventing assigning Servers from one CDN to a DeliveryService on a different CDN.

rawlinp commented on issue #3893: Add a database constraint preventing assigning Servers from one CDN to a DeliveryService on a different CDN.
URL: https://github.com/apache/trafficcontrol/issues/3893#issuecomment-527981579
 
 
   If adding a DB constraint means existing DB violations would make the DB migration fail, then yeah I don't think we can just add a DB constraint. We can however prevent _new_ DB violations via the API. That wouldn't hold the upgrade hostage over the DB state. Or, we in the migration we could just delete the _invalid_ assignments before adding the DB constraint. Either way, I agree it should be discussed on the mailing list. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services