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 -
I have since discovered the xml is so egregiously wrong that fixing it by hand would be a herculean task
1 reply 0 retweets 8 likesShow this thread -
so I'm now writing more code to output my abstract representation as xml to save myself the trouble
1 reply 0 retweets 5 likesShow this thread -
and all of this is in perl
5 replies 0 retweets 10 likesShow this thread -
-
Replying to @bobpoekert
the existing xml is used pervasively throughout the codebase so I want to build something that makes it more useful
1 reply 0 retweets 0 likes
also I hate database libraries, I've had to PR practically every one I've ever used (five so far, in three languages) so I'd rather just do this myself than deal with someone else's problems
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.