Databases
StackOverflow2013
Usersdbo
USAndrew Pendleton
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USAndrew Pendleton
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. POjQuery form generation
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    3. POAlgorithm for determining which words make a phrase popular
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. COSorry, didn't see your comment until just now. They're lists that regularly get compressed and flushed to disk, and later read by other parts of the app. Reads happen more than writes, and the tasks that read them need to be able to deserialize really quickly, so just taking the contents of the file, decompressing it into ram and using it as-is is ideal. A separate set of tasks mutates the lists, and at mutation time, the number of ints that will be added or deleted is known from the start, so a sufficiently-large buffer can be allocated to fit both the current list and the new ints.
      singulars
      1. POContiguous mutable ordered list
      1. USAndrew Pendleton
    2. COThat said, if I were storing uncompressed data, I could just stream through the buckets and zero out pairs of which one had been deleted, which would also avoid the rewrite while not requiring the table, and which would be even better from my perspective. I guess the holy grail that I was looking for was a compact representation of the data that would preserve that facility, but that may not actually exist, and this may well be the next best thing.
      singulars
      1. PO
      1. USAndrew Pendleton
    3. COThis may well end up being the direction I go... deletes are much rarer than additions, so a table of deleted documents may well be the simplest. Certainly, I don't think any of my corpora have had enough deletes that I couldn't easily hold all the deletes in memory as I streamed the buckets.
      singulars
      1. PO
      1. USAndrew Pendleton
 

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