Databases
StackOverflow2013
Usersdbo
USjacobbaer
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USjacobbaer
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. POGraphing statistics over time in Ruby
      singulars
      1. PTQuestion
    3. POSo... this NoSQL thing
      singulars
      1. PTQuestion
    1. VO
      singulars
      1. POSo... this NoSQL thing
      1. USjacobbaer
      1. VTFavorite
    1. COBut it seems the pitfall of this approach is that your own code has to do what Mongo is doing; moving things from the cache to the database, which still allows inconsistencies. Unless you only write to the disk and read from the cache, invalidating as necessary?
      singulars
      1. POSo... this NoSQL thing
      1. USjacobbaer
    2. COAlthough, their Memcache is also backed by MySQL. So the data in the cache isn't consistent, but the persistence layer is, and if something looks wrong you could always reload it from the disk. I saw MongoDB as a way to reap those benefits without having to bother with the plumbing between those layers, but I guess unless you're really not worried about consistency, the best thing must be to feed a cache with an RDBMS. Unless non-SQL data stores are to be avoided entirely, which I have a hard time believing is true, since no-one does it.
      singulars
      1. POSo... this NoSQL thing
      1. USjacobbaer
    3. CO@vol7ron Sorry, I did mean BigTable. I guess what it seems to me is that any time a consumer website gets big enough for me to have heard of it, they're using Memcached or something similar (Reddit just moved to Cassandara). Are they wrong for doing so rather than spending the $$$$$ to scale MySQL appropriately? It seems the level of consistency provided must be good enough for most things, because I've not heard of a large-scale website that hits SQL for every query. (The rule at Facebook is you never, ever hit the disk other than to populate the cache.)
      singulars
      1. POSo... this NoSQL thing
      1. USjacobbaer
 

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