The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
If you want your data as xml from the database, you can do that in the query that pulls the data.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I've seen tables much, much bigger than that storing XML. And sometimes, you just need to store XML without knowing anything about the structure of it, like if it comes from another system and you need it verbatim.
Most interesting approach I've seen is not to use a native XML type, but to compress it to binary, then convert that to base64 and store that in nvarchar columns. Which drowns everything in zeros and probably makes things bigger than storing native, with the added benefit that its practically impossible to query.
Well I worked in the real world where things are not perfect but for which I still must create solutions.
And something that looks like 'xml' and which everyone else from the current developers and the external service provider refers to as 'xml' is in fact xml to me as a relevant term to apply to it to avoid confusion. Regardless of whether it is valid or not. Being a professional I will be sure to note in the code that it is not valid and as such the code I wrote to deal with it was needed.
Being pedantic doesn't change what I said. I have written a lot of code which both validates whether xml is ill-formed and valid such as via XSD/DTD validation and business validation. And I have written and maintained XSDs for years as well.
But none of that changes the meaning of my previous post. Nor that my goal is to deliver business solutions not idealism.
Just not well thought out. But something that follows naturally for over enthusiasm for new technology (not blaming XML but rather that it was 'new' and thus used.)
I remember a project in Germany where 'everything had to be in XML'. It was not overzealous engineers, but marketing that drove this madness. I'm sure today they are in 'blockchain' up to their elbows.
The gun shop where I work uses a specialized product for sales and gun tracking, and lately it's been crashing and losing indices several times daily. I just discovered that this state-of-the-art system is based on a Visual FoxPro database!
How many other products out there are still using long obsolete technologies, I wonder? I've still got a copy of Paradox, if anyone needs it...
Perhaps they just did not understood the essence of a 3rd party software 'putting everything into XML' is to connect it to a queue and process messages with a middleware on the other side, storing everything to standard relational database?
Why do Britishers hate the use of the word gotten so much? Just because it's more commonly used in North America? I'm from this side of the Atlantic and I don't consider it an abomination. In some situations it is much clearer than the potential alternatives.
One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.
The vehemence of some Britons’ scorn for gotten likely has to do with the fact that it has gained ground in British English over the last couple of decades. Many English speakers from outside North America resist the encroachment of so-called Americanisms (many of which, like gotten, are not actually American in origin) on their versions of English, and, for mysterious reasons, some feel especially strongly about gotten.