Re: additional json functionality
От
David E. Wheeler
Тема
Re: additional json functionality
Дата
Msg-id
BE0F10AF-F691-4F3E-B364-573E14417E74@justatheory.com
Ответ на
Re: additional json functionality (Andrew Dunstan)
Список
Дерево обсуждения
additional json functionality Andrew Dunstan <andrew@dunslane.net>
Re: additional json functionality Craig Ringer <craig@2ndquadrant.com>
Re: additional json functionality Merlin Moncure <mmoncure@gmail.com>
Re: additional json functionality Andrew Dunstan <andrew@dunslane.net>
Re: additional json functionality Merlin Moncure <mmoncure@gmail.com>
Re: additional json functionality Andrew Dunstan <andrew@dunslane.net>
Re: additional json functionality Merlin Moncure <mmoncure@gmail.com>
Re: additional json functionality Andrew Dunstan <andrew@dunslane.net>
Re: additional json functionality Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: additional json functionality "David E. Wheeler" <david@justatheory.com>
Re: additional json functionality Andrew Dunstan <andrew@dunslane.net>
Re: additional json functionality "David E. Wheeler" <david@justatheory.com>
Re: additional json functionality Garick Hamlin <ghamlin@isc.upenn.edu>
On Nov 15, 2013, at 2:02 PM, Andrew Dunstan wrote: > Yeah, it would be a total foot gun here I think. > > I've come to the conclusion that the only possible solution is to have a separate type. That's a bit sad, but there it is. The upside is that this will make the work Teodor has mentioned simpler. (Desperately making lemonade from lemons here.) Fine. My bikeshedding: Call the new type "jsonb". “B” for “binary.” Also, the old one is implicitly "jsona". Get it? David
В списке pgsql-hackers по дате отправления
