We do it the other way (and I’ve always seen it done this way): database change ... | Hacker News

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

		daigoba66 on April 9, 2020 \| parent \| context \| favorite \| on: Deploys at Slack We do it the other way (and I’ve always seen it done this way): database change is compatible with current code and new code. So deploy the database change, then deploy the code change. It usually allows you to rollback code changes.

sciurus on April 9, 2020 [–]

This is generally harder to pull off though unless you do things like force all DB access to go through stored procedures.

And then you're really still pursuing the same strategy described above, except for your stored procedures instead of your app code.

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