Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Another option is to serialize to json. <strike>I do not know about performance, but</strike> I just compared the output when serializing a fairly complex list of entities to json vs. xml, and json is much more compact. Using json the resulting string was 1301303 bytes. With xml, 2429630. So it's almost half the size using json. </p> <p>Below is the helper class I use when serializing/deserializing to json.</p> <p><strong>EDIT</strong><br> I did some performance testing, and it actually turns out that json is faster as well. With xml, serializing 10000 objects took 636 milliseconds, with json only 257. Does anybody know if there are reasons not to choose json over xml?</p> <p><strong>EDIT</strong><br> Tested again, with real data this time:<br> (1000 objects)<br> Uncompressed json: 605 kb<br> Uncompressed xml: 3,53 MB (!)<br> Zipped json: 28,5 kb<br> Zipped xml: 69,9 kb<br> Performance when using pre-initialized serializer:<br> json: ~350 ms<br> xml: ~120 ms </p> <pre><code>using System; using System.Net; using System.Windows; using System.Windows.Controls; using System.Windows.Documents; using System.Windows.Ink; using System.Windows.Input; using System.Windows.Media; using System.Windows.Media.Animation; using System.Windows.Shapes; using System.IO; using System.Text; using System.Runtime.Serialization.Json; namespace GLS.Gui.Helper { public static class SerializationHelper { public static string SerializeToJsonString(object objectToSerialize) { using (MemoryStream ms = new MemoryStream()) { DataContractJsonSerializer serializer = new DataContractJsonSerializer(objectToSerialize.GetType()); serializer.WriteObject(ms, objectToSerialize); ms.Position = 0; using (StreamReader reader = new StreamReader(ms)) { return reader.ReadToEnd(); } } } public static T Deserialize&lt;T&gt;(string jsonString) { using (MemoryStream ms = new MemoryStream(Encoding.Unicode.GetBytes(jsonString))) { DataContractJsonSerializer serializer = new DataContractJsonSerializer(typeof(T)); return (T)serializer.ReadObject(ms); } } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POSilverlight IsolatedStorage techniques for larger files?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHenrik Söderlund
    1. USHenrik Söderlund
    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
    1. COOut of curiosity, have you compared the file sizes of *zipped* xml and json?
      singulars
      1. PO
      1. USRob Fonseca-Ensor
    2. COI did, and the results were pretty much the same. But that was with test data only. My data entities were named "entity 1", "entity 2" etc. up to 10000. With that much repeated data I got a compression rate of about 99%. I think the zipped json file was about 13kb and the xml was around 28kb. But to get useful results I would have to start playing around with real data, or at least randomizing names, child collections etc. And I am just a little too lazy to do that. :)
      singulars
      1. PO
      1. USHenrik Söderlund
    3. COTurns out I wasn't too lazy after all. See the test results in the edited answer.
      singulars
      1. PO
      1. USHenrik Söderlund
 

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