5/2/2023 0 Comments Linux nokia rm 1172IF OBJECT_ID (N'dbo.cleanXMLElements', N'FN') IS NOT NULL This is just for cosmetic purposes – nothing a machine will take a notice of… If the data is only exported (and no ‚translation‘ back in the database is needed), these encoded entities can be replaced with anything looking … better – like the underscore. This is a minor problem cause it just creates ugly element names. It turned out that the conversation is applied to nearly every special character used within column names: By applying this rule a column named ‚Ali Baba‘ will turn into ‚Ali_x0020_Baba‘. To turn these column names into valid XML element names Microsoft decided to convert these characters into their UTF-16 representation surrounded by underscores. Some smart guy decided to use spaces and braces within the column names. While playing with the example databases of Microsoft NAV I recognised some funny things. If you go to use the SQL server as a data source in a business integration orchestration the XML representation of the SQL results turns the mapping of the data between different entities into a point and click game… This is nothing new and special (in the age of NO-SQL and document centric databases) and works well. >select * from dbo.foo for XML RAW, ELEMENTS All recent versions of MS SQL are able to generate the XML representation of a SQL query result on the fly:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |