3 ms·
Agreed, the standardised part is JSON, it's not clear to me that the binary format, to be used internally by each of sqlite & postgres, would benefit from stan
by OJFord 3y ago
Agreed, the standardised part is JSON, it's not clear to me that the binary format, to be used internally by each of sqlite & postgres, would benefit from standardisation?
As an ideal, sure, but what concrete benefit? Some kind of third-party tool/plugin that might hypothetically work with either, bypass the clients, and benefit from a single parser implementation for the internal representation of binary JSON columns?
- paulddraper 3y agoNot for databases but for messages, ala msgpack
- DemocracyFTW2 3y agoSure, maybe, but neither Postgres's nor SQLite's binary format are supposed to ever leak to the outside; it is strictly an implementation detail.
- paulddraper 3y ago> Not for databases
- orf 3y agoWhat’s the thought pattern here? Different implementations of different message formats should have a common format for representing… JSON? Why?
- paulddraper 3y agoUh no. Not multiple formats. Different messaging systems, libraries, etc should use a JSON-equivalent binary format. If you'd like you could say it's messagepack, but it's not because it's a superset of the JSON model, you can't round trip it
- orf 3y agoSo, BSON? https://en.m.wikipedia.org/wiki/BSON https://en.m.wikipedia.org/wiki/BSON But the argument here seems to be that we need “one format to rule them all”, which obviously never works.
- brazzy 3y agoSurely the thing that would benefit from standardization is the SQL-level stuff use JSON values, like indexing, and path expressions.