Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

While I'm very sympathetic to "we accidentally nuked our prod DB" because, let's admit it: we've all been there at some point, I'm also a bit baffled here because I don't think that the problem lies with too much wine, Postgres permissions or scripts on localhosts but the fact that recreating a database by FIRST dropping all tables and THEN recreating them is like deliberately inviting those gremlins in.

But, as I said, that happens and blaming doesn't fix anything, so, for the future:

1. make a temporary backup of your database 2. create tables with new data 3. drop old tables



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: