3 ms·
I really don't see the point of this compared to Postgres' native JSON support. And with things like this in the source https://github.com/microsoft/documentdb
by Eikon 2y ago
I really don't see the point of this compared to Postgres' native JSON support.
And with things like this in the source https://github.com/microsoft/documentdb/blob/a0c44348fb473daf75b8950d0118201c0b3e6d19/pg_documentdb_core/src/planner/selectivity.c#L24 https://github.com/microsoft/documentdb/blob/a0c44348fb473da...
I'd definitely stay away from it.
- Tostino 2y agoAt least they commented it XD. Selectivity is pretty hard to get right though so I can see why they stubbed it out and will deal with an actual implementation later.
- SigmundA 2y agoSince it uses BSON it support more datatypes like date, binary, decimal, etc. Looks like it supports background indexing too. Date and Binary are ones I wish JSONB supported most often.
- jasonthorsness 2y agoThis is the key feature; unless you work with MongoDB you don’t realize the ubiquity of the extra types it supports and how it improves ease of use
- SigmundA 2y agoMy preference would have been for PG to have a hierarchal data type that supported all of its normal data types and then built JSON support on top of that.
- jasonthorsness 2y agoWell at least now that it is open, that sort of thing can be noticed and fixed more easily
- mplanchard 2y agoI guess my question would be how it handles updates, inserts, and deletes on nested components of objects. These operations in postgres’ JSONB can be a huge problem due to needing to lock the entire row.