XML Transforms -- in most all their uses -- much like XML as a database format is just a bloated wreck and disastrously bad idea. Human legible formats like XML are GREAT for data interchange BETWEEN database formats, but absolutely dreadfully inefficient when it comes to actual data procession.
... and no matter what the die-hard "XML for everything" nutters claim, XML exists to be a human legible format, NOT a machine readable one. I don't know where the blue blazes they got the idea that using plain english words in a markup style format is 'machine readable', but it shows that they don't know enough about 'machines' to be opening their traps on the subject. Are the integers and floats stored in bitpacked formats? Are the strings stored as RLL or null-terminated? No? THEN IT'S NOT MACHINE READABLE! (literally my right hand swings up ready to deliver a pimp slap every time a XML nutjob opens their yap on this subject).
Much like the now defunct XHTML 1.1/newer, XSLT was a bad idea put together by people who don't know enough about computers to be making 'standards' for them -- though admittedly I say the same thing about a LOT of recent technologies. They're all grossly inefficient, needlessly complicated, and actually make MORE work than older simpler formats... which is why I put JSON in the same category as XML for most data throughput...
But again, I'm the creepy bastard who's still using ASCII control codes or CSV for data transmission. Don't know why we need all the goofy complex crap like JSON and XML when we have perfectly good character codes for start of heading, start of text, end of text, end of medium, file separator, group separatior, record separator, unit separator... That thanks to every major character encoding being backwards compatible to ASCII7 work JUST FINE to this day.
Hell, the only time you should need to be passing field names is if you don't know the field names -- something that shouldn't be happening in the first place.
Oh, and mySQL got hacked? Lemme guess, still using mysql_ functions with no sanitation? .. and don't go completely back to flat HTML, just use PHP to glue parts together and leverage the filesystem, no SQL needed.
I'm increasingly starting to think that when it comes to databases, we're overusing them now for things where it's a total waste of code and time. Users, massive organized posts? Fine, makes sense... Static content on a site? Not so much.