so over the past couple weeks I wrote a system to read in a postgres schema and an xml definition meant to correspond to that schema
-
Show this thread
-
create abstract representations of both, diff the former against the latter resulting in an ordered changeset to update the database to to the xml, and render it as runnable sql
1 reply 0 retweets 4 likesShow this thread -
the idea being to then update the xml by hand to actually match the database, then in the future all schema changes are done by simply changing the xml, and a utility updates the database to match
2 replies 0 retweets 4 likesShow this thread -
Replying to @alicemazzy
How do you distinguish a column being renamed from in "prior (in-db) schema" to in "new (XML) schema", vs. a new column being added an an unrelated old one being dropped?
1 reply 0 retweets 0 likes -
Replying to @rsthau
I don't, it's just an add and drop. it doesn't matter in practice because we don't rename columns
1 reply 0 retweets 0 likes
the way our release cycle works it would have to be done over the course of two releases anyway because we do database updates against a live system on the previous code
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.