On Thu, Nov 14, 2013 at 2:54 PM, Hannu Krosing <ha...@2ndquadrant.com> wrote: > I am sure you could also devise an json encoding scheme > where white space is significant ;)
I don't even have to think hard. If you want your JSON to be human-readable, it's entirely possible that you want it stored using the same whitespace that was present on input. There is a valid use case for normalizing whitespace, too, of course. Everyone on this thread who thinks that there is Only One Right Way To Do It should take a chill pill. There is, in fact, more than one right way to do it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
