i want to insert arbitrary xml into SQL Server. The xml is contained in an XmlDocument
object.
The column i want to insert into is either nvarchar
, ntext
, or xml
column (If it makes your life easier then you can pick which type it is. Really it's an xml
column).
Prototype
void SaveXmlToDatabase(DbConnection connection,
XmlDocument xmlToSave,
String tableName, String columnName);
{
}
The reason i ask is because i'm trying to find the proper way to turn the XmlDocument
into something the database can take - being sure to keep the encodings right:
- i have to make sure the encoding using during insert matches what the database takes
- i have to synchronize the
<?xml version="1.0" encoding="windows-1252"?>
element
i know ntext
, nvarchar
, or xml
are stored as UTF-16
inside SQL Server. So i have to be sure to give the data to SQL Server as UTF-16. This isn't a problem for String
s in .NET, since they are unicode UTF-16.
The 2nd problem, synchronizing the encoding attribute, is a tougher nut to crack. i have to figure out how to find the declaration element through the XmlDocument
object:
<?xml version="1.0" encoding="windows-1252"?> (or whatever the encoding may be)
and adjust it to `UTF-16
<?xml version="1.0" encoding="UTF-16"?>
My nieve attempt (that fails)
Ignoring the encoding in the xml declaration, and just figuring out how to save anything into SQL Server:
void SaveXmlToDatabase(DbConnection connection,
XmlDocument xmlToSave,
String tableName, String columnName);
{
String sql = "INSERT INTO "+tableName+" ("+columnName+")
VALUES ('"+xmlToSave.ToString()+"')";
using (DbCommand command = connection.CreateCommand())
{
command.CommandText = sql;
DbTransaction trans = connection.BeginTransaction();
try
{
command.ExecuteNonQuery();
trans.Commit();
}
catch (Exception)
{
trans.Rollback();
throw;
}
}
}
This fails because the sql
i try to run is:
INSERT INTO LiveData (RawXML)
VALUES ('System.Xml.XmlDocument')
This is because XmlDocument.ToString()
returns "System.Xml.XmlDocument
". Peeking at the implementation, it see that it literally is call:
this.GetType().ToString();
Aside: Microsoft seems to have gone out of their way to prevent you from getting the Xml as a string - presumably because it leads to bugs (But they don't tell us what bugs, why they're bugs, or the right way to convert an
XmlDocument
into aString
!)