Support for Xml fragments
Options
Could LinqPad work with XML fragments as valid Xml content?
We commonly use Xml columns with MS SQL 2008+ and we store data in this columns as Xml fragments. So no root element is present. This is caused by convention and performance optiomalizations also.
But these columns cannot LinqPad handle and display. In MS SQL, xml fragment is commonly queryable and usable. Can LinqPad handle these columns also?
Example of stored data
Book1
Book2
We commonly use Xml columns with MS SQL 2008+ and we store data in this columns as Xml fragments. So no root element is present. This is caused by convention and performance optiomalizations also.
But these columns cannot LinqPad handle and display. In MS SQL, xml fragment is commonly queryable and usable. Can LinqPad handle these columns also?
Example of stored data
Book1
Book2
Comments
-
Xml was lost, so once again:
Example of stored data<Item>Book1</Item> <Item>Book2</Item>
-
I could add an option to the connection properties to map XML columns to string instead of XElement - would that help?
-
I think it would be useful to have such an option, Joe, so "yes please" from me
Someone also said the same thing on SO: http://stackoverflow.com/questions/40089784/in-linqpad-is-there-a-way-to-serialize-type-xml-column-as-string -
Yes, it would help. Because currently we do not have any simple way how expcude Xml column without explicitly naming all columns in select clause without xml columns. Thanks!
-
This feature is now implemented in the latest beta:
http://www.linqpad.net/download.aspx#beta
Right-click the connection, properties, advanced. -
Thank you!
