Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>DataSet.GetXml()</code> returns a <code>string</code>. In .NET, strings are internally encoded using UTF-16, but that is not really relevant here.</p> <p>The reason why there's no <code>&lt;?xml encoding=...&gt;</code> declaration in the string is because that declaration is only useful or needed to parse XML in a <em>byte stream</em>. A .NET string is not a byte stream, it's just text with well-defined codepoint semantics (which is Unicode), so it is not needed there.</p> <p>If there is no XML encoding declaration, UTF-8 is to be assumed <em>by the XML parser</em> in the absence of BOM. In your case, however, it is also entirely irrelevant since the problem is not with an XML parser (XML isn't parsed by SQL Server when it's stored in a <code>TEXT</code> column). The problem is that your XML contains some Unicode characters, and <code>TEXT</code> is a non-Unicode SQL type.</p> <p>You can encode a <code>string</code> to any encoding using <code>Encoding.GetBytes()</code> method. </p>
    singulars
    1. This table or related slice is empty.
    1. PO.NET DataSet.GetXml() - what's the default encoding?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USPavel Minaev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO.NET DataSet.GetXml() - what's the default encoding?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COWrong assumption, the column is not TEXT, only a parameter of type TEXT is being used to accept the XML string; TEXT is used because varchar(8000) has a restriction on length; The problem *is* with the parser on sqlserver. Server: Msg 6603, Level 16, State 1, Procedure sp_xml_preparedocument, Line 40 XML parsing error: An invalid character was found in text content. As i said, when i declare the XML string as ISO-8859-1, no error occurs on the sproc, so the parser is treating ASCII 146 as acceptable.
      singulars
      1. PO
      1. USjoedotnot
    2. COThe problem is still `TEXT`, actually. Specifically, when you pass a Unicode `string` to your sproc, it has to be converted to non-Unicode encoding to match `TEXT`; the result is of course not encoded using UTF, and which encoding it is going to use to convert isn't easy to determine. If you have control over sproc, just replace `TEXT` with `NTEXT`, and don't bother with ancodings
      singulars
      1. PO
      1. USPavel Minaev
    3. COI arrived at the same conclusion to use NTEXT just prior to reading your last comment, then i won't need to declare <br/> ?xml version="1.0" encoding="ISO-8859-1"?<br/> to make it work (or won't need to bother with encodings as you have said). Can you please just clarify a few things:<br/> are you saying if i use NTEXT, the xml string that i pass will be interpreted by the xml parser as UTF-16? <br/>why does keeping TEXT and declaring the xml string as ISO-8859-1 works?
      singulars
      1. PO
      1. USjoedotnot
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload