3 ms·
I used XSLT for somewhat similar purposes twice upon a time. It hurts to realize that that was 20+ years ago, but I was producing many dozens of megabytes of co
by ergonaught 4y ago
I used XSLT for somewhat similar purposes twice upon a time. It hurts to realize that that was 20+ years ago, but I was producing many dozens of megabytes of complex SQL and PL/SQL. There was no way to do that "on time" while writing everything by hand, and "refactoring" would have been laughable.
- cfeduke 4y agoI did something similar when I figured out XSLT was for more than just front-end stuff. And I was working with Oracle as the database too; these enterprise code bases acquire huge amounts of often poorly written SQL and it feels like making at least some of the repeated queries DRY would help - but later you realize the people who need to maintain this system when you're gone are the same people who came up with the spaghetti queries in the first place.
- usgroup 4y agoCould you say a bit about how you'd manage a SQL repo using XSLT? It isn't obvious to me how that works.
- cryptonector 4y agoNot OP but I reckon OP would have XML documents from which to generate SQL schema and queries, with one XSL for generating schema, and one or more XSLs for generating queries. You could do the same with jq.