4 ms·
The first 90% of my current pymongo-backed project was great, I just came up with whatever schemas I wanted and inserted the data as serialized JSON-style objec
by dpritchett 15y ago
The first 90% of my current pymongo-backed project was great, I just came up with whatever schemas I wanted and inserted the data as serialized JSON-style objects.
The second 90% has been not so great... I spend my time either doing in-place serialized batch updates to correct my own early schema mistakes or (mostly) reinventing SQL so that I can join my schemas arbitrarily and dump them to CSV per user requests.
I hope this means I'm just doing it wrong. Time to dig my Mongo book back out.
- Pewpewarrows 15y agoNope, unfortunately that's what I'm running into as well. A blissful start of the project with no schemas to tie it down or hold it back. Now that it's starting to require migrations, join-like behavior, and complicated queries, I really just wish I had my trusty old PostgreSQL back. I swear, if I have to write one more set of map/reduce functions just to do anything non-trivial with this database I'm going to end up hurting a small animal.
- deleted 15y ago[deleted]
- fdr 15y agoIf you could imagine designing Postgres to be more enjoyable and productive to use in the earlier stages, what would you want?