3 ms·
In the general case, it has the low startup cost of a document db combined with a clear path to scalability with a future relational model. In the specific cas
by jared314 14y ago
In the general case, it has the low startup cost of a document db combined with a clear path to scalability with a future relational model.
In the specific case, it removes the data transformation code required to convert the clojure data structures I have to sql, json, or xml that postgresql understands.
- jacques_chester 14y agoSo the same argument as (say) YAML, Lua tables or TNetStrings. Or, if you include binary representations, stuff like Thrift, XDR and ASN.1. You can embed a JVM in PostgreSQL and write the functions yourself (or use PL/Scheme I suppose), but I would be basically amazed if anyone decides to do it for you. JSON gets the nod because it's understood by billions of systems. Other formats are going to struggle.
- jared314 14y agoWell, when you say it that way, I guess I must be wrong to want things that simplify my life as a developer.
- jacques_chester 14y agoIt just seems like a particularly parochial wish, is all. And in life we rarely get what we want because potential ends are limitless and means limited.
- jared314 14y agoIt is a small wish, and you are trolling.
- jacques_chester 14y agoIt is not a small wish to ask them to take on supporting a serialisation format. They will need to integrate it into the core code and it will need to be supported indefinitely. I asked because I wanted to know if there was a particular reason for your wishes -- which is, as I said, quite parochial compared to the reach of JSON -- over other potential priorities. If asking questions is "trolling", I'll be over here with 4chan and Socrates.