If you're talking about storing business logic in the database for building an MVP, e.g. using stored procedures and views in your app, then yeah, go for it. Deal with the existential risk (your business might not work) before you deal with the risk of needing to fix tech debt.

If you have the resources to avoid putting business logic in the database, in a production app context, I'd avoid it if possible. It's just another thing tying you to that database, and if you ever decide to migrate, it's another hurdle preventing you from doing that.