Comments on Ruby, Javascript, Erlang blog: Snakes, Gems & Coffee: DRAFT: Why proponents of marriage equality should ...

This blog post series was in response to Sam Hughs...

2010-08-13T17:00:33.600-05:00

This blog post series was in response to Sam Hughs' blog post on designing RDBMS schemas to model marriage for various cases. It is an excellent article, but it was only focused on RDBMS schema modelling. He is located in the UK and may have had to model such a situation at work since the UK passed civil partnerships with the same legal benefits as married couples. I would not speculate about anyone else's sexual orientation when his treatment of the topic is clearly technical and not about the social issue. You should definitely check it out, as it is very thorough for the topic it sets out to handle (RDBMS schema design):
http://qntm.org/gay

The purpose of my response was to introduce concepts of graph databases to those who have a relational database background. I hope my treatment of the technical content wasn't so lame that this wasn't accomplished? If so, please provide feedback. I am still intending to write a concluding part 3 to discuss what we have learned about the pros and cons of using a graph database to model this domain problem.

The challenge of modelling marriage including same sex partnerships or even poly amorous groups in this context is purely a technical one. Legal or other non-technical discussions should be had elsewhere as they aren't appropriate for this blog.

Thanks,
Susan

You bring the topic up a lot, so just curious... a...

2010-08-13T15:46:09.724-05:00

You bring the topic up a lot, so just curious... are you gay?

@ahzf absolutely. Many of these concepts will len...

2010-04-04T11:50:12.906-05:00

@ahzf absolutely. Many of these concepts will lend themselves more generically across graph database implementations. Neo4J is simply the graph database that I experimented with so far:)

Actually I think defining a traverser is also a (h...

2010-04-04T05:14:23.954-05:00

Actually I think defining a traverser is also a (high-level) declarative way to query navigational databases like (most) graph databases. Just add a grammar parser and some syntactic sugar to you solution and you hav a NeoQL ;) Btw, most academic graph databases do it this way.