![]() I can surely see it is similar but slightly different. I wrote the same query as shown: SELECT 1 as '.SQLAuth',2 as 'SQLAuth.Pinal'Ĭolumn name ‘.SQLAuth’ contains an invalid XML identifier as required by FOR XML ‘.'(0x002E) is the first character at fault. I wanted to see what the error would be using the same mistake with XML PATH. Remedy: as a corrective action, I fixed column alias to conform to FOR JSON PATH rules. The name of one of the column starts or ends with dot. An error is reported when illegal characters are found in the column or column alias used in FOR JSON PATH. This is when I realized the mistake I had made. This error was generated by the following command shown in the image below: ![]() ![]() Column name or alias that contains ‘.’, starts or ends with ‘.’ is not allowed in query that has FOR JSON clause. Property ‘.SQLAuth’ cannot be generated in JSON output due to invalid character in the column name or alias. When working with the FOR JSON PATH, I got the below error: You will want to do your own customization and there would be multiple learnings of using the same. Not everytime the defaults will work when working with databases like SQL Server. Let us see how to fix error 13603 while working with JSON documents. This is something I stumbled accidentally when using JSON constructs. I wanted to write about some of the interesting errors one will get when using JSON custom paths. ![]() In this blog, I have written on a number of articles on JSON which you can take a look at. ![]() Working with new data types is something we need to evolve. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |