Flutterby™! : Mongo vs Postgres

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Mongo vs Postgres

2018-02-21 22:27:02.598609+01 by Dan Lyke 0 comments

Why We Moved From NoSQL MongoDB to PostgreSQL. One of their reasons, needing to check for existence in the record because not all records have a field, is a bad one. And restructuring a large database can take an unacceptable amount of time (work is currently dealing with this issue in old MySQL databases and our archive policies around that), but it's still a good set of things to consider about NoSQL before you hitch a wagon to it.

[ related topics: Open Source Work, productivity and environment Databases ]

comments in ascending chronological order (reverse):

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.