We deleted the production database by accident

>Note that host is hardcoded to localhost. This means it should never connect to any machine other than the developer machine. We’re too tired to figure it out right now. The gremlins won this time.

Obviously, somehow the script ran on the database host.

some practices I've followed in the past to keep this kind of thing from happening:

* A script that deletes all the data can never be deployed to production.

* scripts that alter the DB rename tables/columns rather than dropping them (you write a matching rollback script ), for at least one schema upgrade cycle. you can always restore from backups, but this can make rollbacks quick when you spot a problem at deployment time.

* the number of people with access to the database in prod is severely restricted. I suppose this is obvious, so I'm curious how the particular chain of events in TFA happened.

Re: We deleted the production database by accident

#8

Post by rmrfrmrf » Sat, Oct 17, 2020, 11:39 PM UTC

smadge wrote: post #2

SSH tunnel from localhost to prod on database port?

vscode remote extension perhaps

Re: We deleted the production database by accident

#9

Post by xwdv » Sat, Oct 17, 2020, 11:39 PM UTC

rullelito wrote: post #4

LOL, I forgot how few safety measure startups have in place.

Given the short time frames that startups aim to capture value in its not worth investing time in safety until you have plenty of capacity to spare later.

Re: We deleted the production database by accident

#10

Post by freitasm » Sat, Oct 17, 2020, 11:40 PM UTC

Lost seven hours of data? Daily backup with no transaction log backup?

Whoa.