Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POSuggestion for Ancestry type Database: MongoDB, Redis, etc.?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USalexpopescu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSuggestion for Ancestry type Database: MongoDB, Redis, etc.?
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI played around with neo4j and it really seems very slick. Not a huge fan of their licensing though. Thing is a document databse like mongodb is perfect for the rest of my app, so I'll either be leveraging mongodb for everything or I'll mix in another solution just for the ancestry data. would a graph database give me any advantages over redis sets? Seems like a graph db would be overkill.
      singulars
      1. PO
      1. USDave Rapin
    2. COIt's impossible to say if it is overkill if there's no context of what your app does. When using a non relational database there are two things you need to consider upfront: how you store data and how you access it. The 2nd part is missing from your description so it's impossible to answer. Will you need to navigate the relations deeper than 1 level (that's what you can get with Redis or Twitter's FlockDB)? More generically, the more you need to navigate the relationships and discover aspects of it then the more a graph db makes sense.
      singulars
      1. PO
      1. USalexpopescu
    3. COWell I've been researching the topic quite a bit since posting. Essentially I'm dealing with a DAG (Directed Acyclic Graph). Neo4j (and possibly other graph DBs) definitely seem like the best fit for traversing the nodes. Users will be able to add a node (father if one doesn't exist, mother if one doesn't exist, and multiple children) to any given node and the system will render a visualization of the graph up to a certain depth, let's say a radius of 3 in any direction from the focused node. So I'd be traversing up to 3 nodes away. Definitely starting to sound like a graph db problem.
      singulars
      1. PO
      1. USDave Rapin
 

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