I suspect the term "table" is clouding things a bit. I've been trying
to avoid using RDBMs terms when thinking and talking about Couch.
Having a document per relationship makes the most sense to me, in this
case.
That said, user relationships fit really well on top of an RDBMS (at
least, the particular case we're discussing here). I suspect whatever
you end up doing is going to feel a bit dirty in Couch. When you get
a bit deeper into a social graph, the RDBMs falls down completely,
though.
On Jul 22, 2008, at 2:17 PM, Patrick Aljord wrote:
On Tue, Jul 22, 2008 at 11:33 AM, Jan Lehnardt <[EMAIL PROTECTED]> wrote:
Your gut feeling was correct, it is a bad idea.
So you're in disagreement with Damien Katz? Who should we trust more?
You or the creator of couchdb? :D More seriously, I'm interested too
about your opinion about this.
