Replies: 1 comment 1 reply
-
(I guess that the implementation really is vendor specific, targeting PostgreSQL, but from a cursory view, it should be relatively simple to abstract the implementation away; all that's needed is a diff provider for the specific SQL flavour) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Over the past few days, I've been looking for a more declarative way of managing a plain SQL project. In a perfect world, I'd prefer to define the desired state rather than how to get there. However, there seems to be few ways to do this while writing plain SQL at the moment. I've found that sqitch will probably get me closest.
In my research, I came across a blog post where the author, @matthieu-foucault , was able to get close while remaining vendor-agnostic. The product of his efforts, a proof of concept called postgit, is available on GitHub but seemingly unmaintained.
Even so, I think his efforts were interesting and perhaps somewhat in alignment with sqitch's goals as well. Perhaps there are even ideas that could be reused by sqitch directly, such as support for automated migration generation using a diff tool?
Beta Was this translation helpful? Give feedback.
All reactions