Re: hstore ==> and deprecate =>
От | Robert Haas |
---|---|
Тема | Re: hstore ==> and deprecate => |
Дата | |
Msg-id | AANLkTimxUsfnfWhXTRw_2zxsraDD6o-Tg1ocvMAJi8mw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: hstore ==> and deprecate => (Andrew Gierth <andrew@tao11.riddles.org.uk>) |
Ответы |
Re: hstore ==> and deprecate =>
|
Список | pgsql-hackers |
On Mon, Jun 14, 2010 at 4:35 PM, Andrew Gierth <andrew@tao11.riddles.org.uk> wrote: > I'm happy with deprecating the first two => in favour of hstore() if > that is in line with general opinion. The hstore => text[] slice could > be replaced by another operator name; the existing name comes from the > analogy that (hstore -> text[]) returns the list of values, whereas > (hstore => text[]) returns both the keys and values. So, I kind of like Florian Pflug's suggestion upthread of replacing hstore => text by hstore & text[]. I think that's about as mnemonic as we're likely to get, and it gels nicely with the hstore ?& text[] operator, which tests whether all of the named keys are present in the hstore. Does anyone want to bikeshed further before I go do that? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: