Re: [HACKERS] jsonb problematic operators
От
Tom Lane
Тема
Re: [HACKERS] jsonb problematic operators
Дата
Msg-id
20158.1481653511@sss.pgh.pa.us
Ответ на
Re: [HACKERS] jsonb problematic operators (Nico Williams)
Список
Дерево обсуждения
[HACKERS] jsonb problematic operators Jordan Gigov <coladict@gmail.com>
Re: [HACKERS] jsonb problematic operators Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] jsonb problematic operators Andres Freund <andres@anarazel.de>
Re: [HACKERS] jsonb problematic operators Geoff Winkless <gwinkless@gmail.com>
Re: [HACKERS] jsonb problematic operators Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] jsonb problematic operators Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] jsonb problematic operators Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] jsonb problematic operators Merlin Moncure <mmoncure@gmail.com>
Re: [HACKERS] jsonb problematic operators Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] jsonb problematic operators Greg Stark <stark@mit.edu>
Re: [HACKERS] jsonb problematic operators Michael Paquier <michael.paquier@gmail.com>
Re: [HACKERS] jsonb problematic operators Nico Williams <nico@cryptonector.com>
Re: [HACKERS] jsonb problematic operators Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] jsonb problematic operators Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] jsonb problematic operators Matteo Beccati <php@beccati.com>
Re: [HACKERS] jsonb problematic operators Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] jsonb problematic operators Geoff Winkless <gwinkless@gmail.com>
Re: [HACKERS] jsonb problematic operators Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] jsonb problematic operators "David G. Johnston" <david.g.johnston@gmail.com>
Re: [HACKERS] jsonb problematic operators Geoff Winkless <pgsqladmin@geoff.dj>
Re: [HACKERS] jsonb problematic operators Merlin Moncure <mmoncure@gmail.com>
Re: [HACKERS] jsonb problematic operators "David G. Johnston" <david.g.johnston@gmail.com>
Nico Williams writes: > On Tue, Dec 13, 2016 at 10:26:24AM +0900, Michael Paquier wrote: >> On Mon, Dec 12, 2016 at 10:22 PM, Greg Stark wrote: >>> One option might be for Postgres to define duplicate operator names >>> using ¿ or something else. >> Are you sure that using a non-ASCII character is a good idea for an >> in-core operator? I would think no. > Eventually language designers will cross that Rubicon in mainstream > languages. And why not? Because it will create all sorts of character-set-conversion hazards. In the current design of Postgres it flat out would not work, because template0 has to be encoding-agnostic. regards, tom lane
В списке pgsql-hackers по дате отправления
От: ronan.dunklau@dalibo.com
Дата: