Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A file format similar to CSV seems fitting, and of course you can use whatever delimiter you'd like in your file, you just need to "escape" the characters used if they are present in the data you are storing.</p> <p>If you do not feel like escaping individual characters you can use an encoding scheme that doesn't ouput any of the delimiters you have chosen to use, such as <a href="http://en.wikipedia.org/wiki/Base64" rel="nofollow">Base64</a>.</p> <hr> <h2>My dad is stronger than yours!</h2> <p>What file schema is "the best" depends on so many circumstances. As an example; I'm in love with JSON when it comes to sending smaller chunks of data between a client and a server.</p> <p>Though I'd think both once and twice before using it in a flat-file schema, especially if there is a lot of data to be contained in there.</p> <p>JSON is to some extend human readable, which is great for debugging, though not as great for so much else.</p> <p>XML is a great format, and I like the idea behind it though it's way too complex.</p> <p>CSV files or similar patterns following the same idea is my 5 cents.</p> <hr> <h2>Sample flat-file schema</h2> <p>id | epoch | short string | url | large description  </p> <pre><code> | -&gt; ; (delmiter) id -&gt; matching /^[0-9]+$/ epoch -&gt; matching /^[0-9]+$/ (also known as unix timestamp) url -&gt; Urls should not contain raw ';', (explicitly check before input) short string -&gt; Normalized large desc. -&gt; Normalized </code></pre> <p>Normalized in the above just means a method of sanitizing the data so that it doesn't interfere with parts of our schema.</p> <p>Escaping <code>;\r\n</code> is what we need to make this work, or just, as mentioned earlier, use an encoding algorithm such as Base64.</p> <p>You should keep in mind in what order you'd like to store your data. If you'd like to parse out <code>url</code> more often then <code>epoch</code> it could be a good idea to put that as far to the left of the line as possible.</p> <p>If you'd like to have easy/fast searching you could/should store all "large descriptions" in a separate file, and only fetch/process that data when it's required.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat's the best flat-file format to hold structured data?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFilip Roséen - refp
    1. USFilip Roséen - refp
    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
    1. COThis is not a bad idea considering my dataset will be at most 10 megabytes (tens of thousands of rows). I'm just not comfortable with using a random delimiter and escaping characters. But I should probably just get over that.
      singulars
      1. PO
      1. USoxuser
    2. CO@oxuser normalize your data by using a encoding algorithm such as Base64 (mentioned/linked in the post), then you don't have to worry about colliding delimiters and such.
      singulars
      1. PO
      1. USFilip Roséen - refp
    3. COOh nice I never knew about this. What is Base64 usually used for? Purposes like this?
      singulars
      1. PO
      1. USoxuser
 

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