12 ms·
I apologize for being short with you in my previous response. I need to be better about assuming good faith. Your response seems to betray a certain ignorance
by pleoxy 3y ago
I apologize for being short with you in my previous response. I need to be better about assuming good faith.
Your response seems to betray a certain ignorance of mongo. Don't you realize that mongo has indexes?
For handling documents, this blog post covers the topic in some depth.
https://jimb-cc.medium.com/postgres-jsonb-meets-mongodb-part-1-the-basics-43d9fc95c40b https://jimb-cc.medium.com/postgres-jsonb-meets-mongodb-part...
Might I suggest you actually use mongo on a project before engaging further on the topic. It clearly has had a lot more thought put into it in the context of json documents.
If postgres works great for your use cases, great, go be happy with the tool.
- cpursley 3y agohttps://www.dbvis.com/thetable/postgresql-jsonpath/ https://www.dbvis.com/thetable/postgresql-jsonpath/ https://github.com/obartunov/sqljsondoc/blob/master/jsonpath.md https://github.com/obartunov/sqljsondoc/blob/master/jsonpath...
- pleoxy 3y agoDefinitely a better solution than the brick wall he hit. Complicated beastie. I can see the appeal if you just love, eat, and breath SQL. But a query language within a query language feels bolted onto something alien to do something pretty basic. Pass. If I'm teaching this to new engineers, pass also.