Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>How important is it that the resulting file be human-readable? If it's mostly there to be read later by the program, you should definitely use serialization:</p> <pre><code>public void SaveArray (string[] array) { NetDataContractSerializer serializer = new NetDataContractSerializer(); using (FileStream file = System.IO.File.Create(_filename)) { serializer.Serialize(file, array); } } </code></pre> <p><strong>Edit:</strong></p> <p>To summarize the advantages of this method over the other two suggested below, the first being using a StringBuilder to concatenate a big string and then saving it to disk, and the second using WriteAllLines to write the string array to disk:</p> <p>The first method will completely lose fidelity to the original list of strings, since it will glob them together into one string. Can you separate them later? Are there well-known delimiters between them? Not necessarily. It's more efficient than just calling + between them, but it's not a good way to store them.</p> <p>The second method is better, since each string will be saved to a different line, and can be read back with ReadAllLines, but you're still on shaky ground here. What happens if any string contains the NewLine character? It will be one string when written, but two different strings when read back. Again, calling WriteAllLines/ReadAllLines relies on newlines being good delimiters, when that's not necessarily the case.</p> <p>Using a serializer - and it doesn't matter if it's the NetDataContractSerializer, BinaryFormatter or any other - will maintain full fidelity with your original data structure, with only a little bit of overhead.</p>
    singulars
    1. This table or related slice is empty.
    1. POSave array to file
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAvner Shahar-Kashtan
    1. USAvner Shahar-Kashtan
    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. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe resulting file is not intended to be human-readable. So what is the best way? Serialization, string builder or File.WriteAllLines and .ReadAllLines?
      singulars
      1. PO
      1. USGarry
    2. COStringBuilder isn't the right way. It's a better way of concatenating strings together, but that's not answering your original question, it's just giving you a more efficient method of doing things the wrong way. :)
      singulars
      1. PO
      1. USAvner Shahar-Kashtan
    3. COSerialization is the safest way when you need to recreate the same string array later. Using WriteAllLines, you'd have problems if any of the strings contained NewLine characters - they would be read differently than they were written.
      singulars
      1. PO
      1. USAvner Shahar-Kashtan
 

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