Sometimes for personal projects (and one client gig) I use the same database for local development and production.

Why?

Because I am a piece of shit.

Holy shit

I don't see a problem... I do this too. whats the issue so long as it isn't public accessible before it's production ready? Right? And most projects you would drop the tables and re-init before it goes live.

@agaskins glad to hear it’s not as appealing as I think.

I usually add a column to each table with whatever environent the input is coming from; production, beta, staging or local. Just for shits n giggles.

This is terrible haha

@SSDD oh, wait.... So you're saying you are using live in-the-wild production DBs with multiple (experimental and production?) versions of the same system? I dunno about that... Why not just make another database, or at least use table prefixes if that's not an option. That would be magnitudes more safe, better for performance and possibly less hassle than the extra column thing. But maybe I'm not seeing the whole picture still. But whatever works at the end of the day, haha. we all have some weird lazy shit we do now and then I guess... If you get paid you can make your own rules ha

Unfortunately, this is very common even at companies. One where I worked had no dev dbs for years while I was there.

We almost had a number of disasters because of it haha.