MongoDB queries don’t always return all matching documents

Re:MongoDB queries don’t always return all matching documents by nevi-me on Wednesday June 08, 2016 @01:13AM (#11860179)

Well, I have used one and had that assertion. Ease of use means making something that works. It seems we're condoning lack of knowledge or experience with programming. If you've never used databases in your life, whether you're using SQL orNoSQL you'll likely end up with rubbish data. In the SQL world it could be that you're storing time in the wrong format, concatenating long fields, or not normalising when you should or the other way around.

In NoSQL you could be reinventing the wheel, or storing data that you can't query efficiently because you can't index it well etc.

All the excuses of not using some document stores beyond ACID really sound like people won't know what the heck they're doing.

[ Parent | on HN ]

Re:MongoDB queries don’t always return all matching documents by catnaroek on Wednesday June 08, 2016 @02:46AM (#11860468)

> Well, I have used one and had that assertion. Ease of use means making something that works.

For me, it means, under no circumstance, no interleaving of transactions or scheduling of commands, nothing, nichts, nada, can the database be in a state where a business rule is violated. If I need to worry what silly intermediate transaction state can be observed from another transaction, or if I need to worry whether a master record can be deleted without cascade-deleting everything that references it, then the DBMS has failed me.

> not normalising when you should or the other way around.

I've never seen a situation where anything less than 3NF (actually, ideally, at least EKNF) is acceptable.

[ Parent | on HN ]