graywolf on Nostr: npub1fzx00…wt6h3 We considered this approach as well, and the limiting factor seems ...
npub1fzx00c36ny4whyuhg4ykx6987wxp885fmwmc784n27qcu6pavwzs3wt6h3 (npub1fzx…t6h3) We considered this approach as well, and the limiting factor seems to be tooling. How to properly version the code? How to deploy it? How to rollback? How to make sure you have the same version in all instances of your database? How to do monitoring? Logging? Testing? For all these questions, these is an answer in the form of tooling for the "traditional" container-based applications, however for deploying, reviewing, developing, ... the store procedures, there does not seem to be widely used option (assuming there even is).
There is an other approach, you could still have traditional application, and just ditch the ORM and write SQL by hand. For golang, there is also sqlc, which seems to be fairly reasonable generator (basically just making golang functions from your SQL code, ensuring type safety).
Just to be clear, I am not saying "do not do it", do what you want :) I am just putting out there what did work for us.
Also, if you want to go full crazy, there is also a PostgREST: https://postgrest.org/en/stable/ :)
There is an other approach, you could still have traditional application, and just ditch the ORM and write SQL by hand. For golang, there is also sqlc, which seems to be fairly reasonable generator (basically just making golang functions from your SQL code, ensuring type safety).
Just to be clear, I am not saying "do not do it", do what you want :) I am just putting out there what did work for us.
Also, if you want to go full crazy, there is also a PostgREST: https://postgrest.org/en/stable/ :)