Hello!
The comments on this profile are unclaimed and thus are unverified.
Do they belong to you? Claim these comments.
lobo_tuerto
Is this you? Claim Profile »
3 days ago
in SQL Databases Are An Overapplied Solution (And What To Use Instead) on Adam @ Heroku
Hey Adam,
Sorry if this is a truly newbie question, I'm trying to wrap my head around something like CouchDB.
Let's take a concrete example, invoices and line items. An invoice can have many line items in it.
With a "normal" SQL DB, you would have two tables, say: Invoices, LineItems. And we all know how that works.
With a "document oriented" DB you would have Invoice docs, those docs, would directly contain the line items in them, right?
Is it possible (and/or easy) to do a query to get a report on the best selling line items? how do you work that on CouchDB? since they are all contained within Invoice documents... in a SQL DB you would only run a query on the LineItems table.
Does this question make sense? :)
Sorry if this is a truly newbie question, I'm trying to wrap my head around something like CouchDB.
Let's take a concrete example, invoices and line items. An invoice can have many line items in it.
With a "normal" SQL DB, you would have two tables, say: Invoices, LineItems. And we all know how that works.
With a "document oriented" DB you would have Invoice docs, those docs, would directly contain the line items in them, right?
Is it possible (and/or easy) to do a query to get a report on the best selling line items? how do you work that on CouchDB? since they are all contained within Invoice documents... in a SQL DB you would only run a query on the LineItems table.
Does this question make sense? :)
1 reply
There are instructions online for doing this stuff:
http://www.google.com/search?ie=UTF-8&oe=UTF-8&...
http://sitr.us/2009/06/30/database-queries-the-...