4 ms·
simply checking if you're talking to a production instance could avert something like this. having some metadata in the db about whether the data stored there i
by ammmir 16y ago
simply checking if you're talking to a production instance could avert something like this. having some metadata in the db about whether the data stored there is acting as production and at what version and deployment level, so tests can have a sanity check before destructive activities.
- ammmir 16y agowhy the downvote?
- seldo 16y agoPresumably because the comment is obvious, unhelpful, and somewhat mean-spirited. I don't think anybody here needs a lesson in how to avoid accidentally dropping your production database.
- ammmir 16y agothanks for the explanation, i didn't mean to be evil. my suggestion might be obvious to some, but definitely not everyone, considering this isn't a singular occurrence.