Knex (http://ift.tt/1wiuqh0) has been a dependable tool for database migrations, but I'm at a bit of a loss on how I should go about managing my custom functions, views, and triggers.Managing them in migration files seems crude... it would force me to rollback for any small change I make to a Postgres function... ideally, every function, view, and trigger would have it's own file in my codebase. If a file was edited, the function, view, or trigger would drop then reapply its updated version to the database.PGrebase (http://ift.tt/2f0KGP8) appears to be more in-line with what I want, but a.) has limited community support and b.) is written in Go.This seems like it would be a very common problem for developers to run into, what is the Node Way™ of handling this?
Submitted February 25, 2018 at 02:05AM by samosa_samsara
No comments:
Post a Comment