Re: Well Formed XML not returned using FOR XML (<?xml version="1.0"?>)

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Martin Honnen <mahotrash@xxxxxxxx>
Date: Fri, 12 Jan 2007 18:52:25 +0100

bqsoftware wrote:

The xml that is returned using FOR XML does not return well formed XML. The xml header for example "<?xml version="1.0"?>" is missing.

Query: Select count(*) from dxcg_jobs FOR XML RAW, ELEMENTS
Result: <row>4</row> (Not well formed)

The XML declaration is optional for XML version 1.0 and encoding UTF-8 and UTF-16 so that snippet above can be well-formed without having an XML declaration.

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
.

Prev by Date: Re: Return string containing name of root node?
Next by Date: RE: weird xquery error
Previous by thread: Re: Return string containing name of root node?
Next by thread: Querying xml data with SQL
Index(es):
- Date
- Thread

Relevant Pages

Re: Problem reading UTF-8 encoded files with IXMLDomDocument
... UTF-16 at some point? ... Then you will get an error because XML header tells ... http://www.smartphonedn.com - Smartphone Developer Network ... Why is top-posting such a bad thing? ...
(microsoft.public.pocketpc.developer)
Re: Mysterious xml.sax Encoding Exception
... and it really is valid utf-16 as far as I can tell. ... Unicode XML string to xml.sax.parseString with an encoding declaration ... I upgraded from the standard distribution 2.5.0 to ...
(comp.lang.python)
Re: Mysterious xml.sax Encoding Exception
... and it really is valid utf-16 as far as I can tell. ... Unicode XML string to xml.sax.parseString with an encoding declaration ... It did NOT work for me with the standard 2.5.1 Windows distribution -- ...
(comp.lang.python)
Re: Problem with sp_xml_preparedocument and ntext
... The XML parser doesn't like being lied to. ... When it runs into your declaration that says it's utf-8 it is already parsing utf-16 so it errors out because its is doing the wrong thing. ...
(microsoft.public.sqlserver.xml)
Re: Saving an XDocument object to disk ALWAYS adds the "
... UTF-16, writing in any other encoding is unsafe and non-portable ... And UTF-8 and UTF-16 are trivially distinguished by BOM (since ... XML spec requires an UTF-16 XML document to have a BOM at the ... safe to omit the XML declaration, ...
(microsoft.public.dotnet.languages.csharp)