title: How to handle destroy edge cases
body: <p>Say for example you have two users looking at a page. Both click to delete the same record. Is there a 'rails way' to handle these types of edge cases?</p>
  
  <p>I haven't been able to find out how rails handles this but I know that, by default, whoever clicks later will end up with a record not found error. How can you catch this and know it came from a destroy action on a record that was already deleted? </p>