title: Quick & Dirty Way of Disabling a Particular Foreign Key
body: <p>Ideally I would have a "isActive" field in the table to indicate if a record is active, but it would involve changes in multiple stored procedures to make the field do what it is meant to do. </p>
  
  <p>I came up with a dirty trick, and kind of tempted to carry it out. Since the result set is generated by a few joins, I was thinking of slightly changing the foreign key in one of the tables by appending an "*", "x", or whatever symbol that doesn't usually end up in a key. </p>
  
  <p>Is there anything I should be afraid of?</p>