On Fri, Sep 13, 2013 at 10:08 AM, Chris Travers <chris.trav...@gmail.com> wrote: > On Fri, Sep 13, 2013 at 7:58 AM, Merlin Moncure <mmonc...@gmail.com> wrote: >> Yup. As things stand currently, it's better *not* to make >> serialization-driving composite types which when learning the json >> stuff I did heavily; it was a habit I learned (and had to unlearn) >> from libpqtypes which solves a lot of the same problems for C clients. >> You can *almost* send json back to the database with the same >> elegance as it can be sent out of the database. I see a big future >> for postgres-json with many roadmap improvements; it's a complete game >> change for service call driven database interaction and forward >> thinking developers should realize it essentially obsoletes ORMS. > > > > In your view, would it be better to serialize in the pseudo-nested-csv > (native row/array) formats?
What's your client side stack? merlin -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
