Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>slugster,</p> <p>You may want to consider switching over to XMLSerializer instead. Here is what I have determined over time:</p> <p>The XMLSerializer and DataContractSerializer classes provides a simple means of serializing and deserializing object graphs to and from XML.<br/> <br/> The key differences are:<br/> 1.<br/> XMLSerializer has much smaller payload than DCS if you use [XmlAttribute] instead of [XmlElement]<br/> DCS always store values as elements<br/> 2.<br/> DCS is "opt-in" rather than "opt-out"<br/> With DCS you explicitly mark what you want to serialize with [DataMember]<br/> With DCS you can serialize any field or property, even if they are marked protected or private<br/> With DCS you can use [IgnoreDataMember] to have the serializer ignore certain properties<br/> With XMLSerializer public properties are serialized, and need setters to be deserialized<br/> With XmlSerializer you can use [XmlIgnore] to have the serializer ignore public properties<br/> 3.<br/> BE AWARE! DCS.ReadObject DOES NOT call constructors during deserialization<br/> If you need to perform initialization, DCS supports the following callback hooks:<br/> [OnDeserializing], [OnDeserialized], [OnSerializing], [OnSerialized]<br/> (also useful for handling versioning issues)<br/> <br/> If you want the ability to switch between the two serializers, you can use both sets of attributes simultaneously, as in:<br/></p> <pre><code>[DataContract] [XmlRoot] public class ProfilePerson : NotifyPropertyChanges { [XmlAttribute] [DataMember] public string FirstName { get { return m_FirstName; } set { SetProperty(ref m_FirstName, value); } } private string m_FirstName; [XmlElement] [DataMember] public PersonLocation Location { get { return m_Location; } set { SetProperty(ref m_Location, value); } } private PersonLocation m_Location = new PersonLocation(); // Should change over time [XmlIgnore] [IgnoreDataMember] public Profile ParentProfile { get { return m_ParentProfile; } set { SetProperty(ref m_ParentProfile, value); } } private Profile m_ParentProfile = null; public ProfilePerson() { } } </code></pre> <p>Also, check out my Serializer class that can switch between the two:</p> <pre><code>using System; using System.IO; using System.Runtime.Serialization; using System.Text; using System.Xml; using System.Xml.Serialization; namespace ClassLibrary { // Instantiate this class to serialize objects using either XmlSerializer or DataContractSerializer internal class Serializer { private readonly bool m_bDCS; internal Serializer(bool bDCS) { m_bDCS = bDCS; } internal TT Deserialize&lt;TT&gt;(string input) { MemoryStream stream = new MemoryStream(input.ToByteArray()); if (m_bDCS) { DataContractSerializer dc = new DataContractSerializer(typeof(TT)); return (TT)dc.ReadObject(stream); } else { XmlSerializer xs = new XmlSerializer(typeof(TT)); return (TT)xs.Deserialize(stream); } } internal string Serialize&lt;TT&gt;(object obj) { MemoryStream stream = new MemoryStream(); if (m_bDCS) { DataContractSerializer dc = new DataContractSerializer(typeof(TT)); dc.WriteObject(stream, obj); } else { XmlSerializer xs = new XmlSerializer(typeof(TT)); xs.Serialize(stream, obj); } // be aware that the Unicode Byte-Order Mark will be at the front of the string return stream.ToArray().ToUtfString(); } internal string SerializeToString&lt;TT&gt;(object obj) { StringBuilder builder = new StringBuilder(); XmlWriter xmlWriter = XmlWriter.Create(builder); if (m_bDCS) { DataContractSerializer dc = new DataContractSerializer(typeof(TT)); dc.WriteObject(xmlWriter, obj); } else { XmlSerializer xs = new XmlSerializer(typeof(TT)); xs.Serialize(xmlWriter, obj); } string xml = builder.ToString(); xml = RegexHelper.ReplacePattern(xml, RegexHelper.WildcardToPattern("&lt;?xml*&gt;", WildcardSearch.Anywhere), string.Empty); xml = RegexHelper.ReplacePattern(xml, RegexHelper.WildcardToPattern(" xmlns:*\"*\"", WildcardSearch.Anywhere), string.Empty); xml = xml.Replace(Environment.NewLine + " ", string.Empty); xml = xml.Replace(Environment.NewLine, string.Empty); return xml; } } } </code></pre> <p>Good Luck,<br/> Jim McCurdy</p> <p><a href="http://FaceToFaceSoftware.com" rel="nofollow noreferrer" title="Face To Face Software">Face To Face Software</a> and <a href="http://YinYangMoney.com" rel="nofollow noreferrer" title="YinYangMoney">YinYangMoney</a></p>
    singulars
    1. This table or related slice is empty.
    1. POSilverlight IsolatedStorage techniques for larger files?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJim McCurdy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Jim, great answer. Unfortunately i cannot use the XmlSerializer due to namespace issues and identical looking objects, hence my use of the DCS. And point #3 about the DCS was also good, i'm sure that has caught a few people out in the past :)
      singulars
      1. PO
      1. USslugster
    2. COJim, I know premature optimisation is the root of most evil, but `new DataContractSerializer(typeof(TT))` and `new XmlSerializer(typeof(TT))` are *very* expensive operations. You could cache these in a `static Dictionary<Type, XmlSerializer>` etc if you found that this code was getting slow.
      singulars
      1. PO
      1. USRob Fonseca-Ensor
    3. CORob, Good observation about performance. I'll make your suggested changes in my apps. Thanks...
      singulars
      1. PO
      1. USJim McCurdy
 

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