15

Aaaaand my team leader once again worked directly on the DB without touching the code, so I can't reproduce his local DB on my machine.

JUST WHY

Comments
  • 3
    I stg how fucking hard can it be. If your ORM allows you to work on the DB with migrations, write a migration. If your ORM allows you to work on the DB with models, update the model. Just don't work directly on the fucking DB without writing somewhere the code for it, because, guess what? YOU CAN'T COMMIT A FUCKING DB.
  • 1
    Reverse seed & diff 😂
  • 0
    power move: clone his machine, boot in VM

    bonus points if you do it directly (if possible,) just one long uninterrupted pipe chain of dd > base64 > zip > ssh > unzip > base64 > dd
  • 0
    @IHateForALiving well, you can commit a fucking db
Add Comment