On Tue, Oct 25, 2016 at 3:23 AM, Alvaro Herrera <[email protected]> wrote: > Haribabu Kommi wrote: >> On Mon, Oct 3, 2016 at 3:51 PM, Michael Paquier <[email protected]> >> wrote: > >> Yes, I agree that adding these JSONB utility functions for this view >> is an overkill, but I thought that these are may be useful for some >> users if it is a JSONB type instead of array. > > Peter Eisentraut said he'd like JSON better: > https://www.postgresql.org/message-id/[email protected] > I asked twice about the use of JSON, suggesting an array instead: > https://www.postgresql.org/message-id/[email protected] > https://www.postgresql.org/message-id/[email protected] > > I now think that we should figure out what it is that we want before we > continue to request it to be changed over and over.
That sounds like a good idea. :-) FWIW, I'm -1 on using JSON here. I don't believe that we should start using JSON all over the place just because we can. If we do that, we'll end up with a mishmash of styles, and maybe look silly when JSON is replaced by the new and much better SDGJHSDR format. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
