State Change and NoSQL Databases

Let's take another look at F. L. Stevens spreadsheet with agencies and agents. It's -- of course -- an unholy mess. Why? It's difficult to handle state change and deduplication.
Let's look at state changes.
The author needs URL's and names and a list of genres the agent is interested in. This …
more ...




A NoSQL Conversation

This cropped up recently. It's part of a "replace Mongo with Relational DB" conversation.

I'm going to elide the conversation down to five key points. The three post-hoc nonsensical ideas, and the two real points.

What's (to me) very telling is that someone else published the five reasons in this …

more ...

SQL Hegemony and Document Databases

A surpassingly strange question is this: "How do I get the data out of MongoDB into a spreadsheet?"
The variation is "How can we load the MongoDB data into a relational database?"
I'm always perplexed by this question. It has a subtext that I find baffling. The subtext is this …
more ...



Document Database and Schema Design

As part of coming to grips with CouchDB (and a particularly odious graph-theory problem) I've been looking around for design guidelines, hints and tips.

This MongoDB Schema Design document is quite helpful. The Link vs. Embed section clarifies the essential tradeoff here. In SQL world, link is the only tool …

more ...