From: Robert Haas on 8 Jun 2010 16:17 On Tue, Jun 8, 2010 at 3:56 PM, Michael Glaesemann <grzm(a)seespotcode.net> wrote: > On Jun 8, 2010, at 15:38 , Robert Haas wrote: >> On Tue, Jun 8, 2010 at 3:34 PM, Merlin Moncure <mmoncure(a)gmail.com> wrote: >>> hm. �any chance of a �shorter operator, like '#'? �I kinda agree that >>> hstore_in and the operator don't have to be the same, but requiring >>> three letter token for the two most high traffic operations w/hstore >>> seems off to me. >>> >>> # is currently used for bitwise xor/geo >> >> I'm happy to do whatever the consensus is. �I thought it would be >> easier to remember if the two operators were spelled at least somewhat >> similarly, but I just work here. > > Perhaps > -> That's already in use to mean something else. > Would a colon work? Nope. ERROR: syntax error at or near ":" > (That's enough bikeshedding for me.) Test first, then post? :-) -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "David E. Wheeler" on 8 Jun 2010 17:36 On Jun 8, 2010, at 12:34 PM, Merlin Moncure wrote: > hm. any chance of a shorter operator, like '#'? I kinda agree that > hstore_in and the operator don't have to be the same, but requiring > three letter token for the two most high traffic operations w/hstore > seems off to me. > > # is currently used for bitwise xor/geo Not at all the same. What about ~> ? Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Michael Glaesemann on 8 Jun 2010 16:28 On Jun 8, 2010, at 16:17 , Robert Haas wrote: >> (That's enough bikeshedding for me.) > > Test first, then post? :-) What? :) If I was productively contributing, I wouldn't be bikeshedding, now would I? Michael Glaesemann grzm seespotcode net -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Pavel Stehule on 9 Jun 2010 03:14 2010/6/8 Tom Lane <tgl(a)sss.pgh.pa.us>: > Pavel Stehule <pavel.stehule(a)gmail.com> writes: >> p.s. I hope so in 9.1 will be complete hstore module marked as deprecated > > Really? And replaced with what? And why wouldn't the replacement use > the same operator names? > We talked about integrated hash tables support. regards Pavel > regards, tom lane > -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Michael Glaesemann on 8 Jun 2010 15:56
On Jun 8, 2010, at 15:38 , Robert Haas wrote: > On Tue, Jun 8, 2010 at 3:34 PM, Merlin Moncure <mmoncure(a)gmail.com> wrote: >> hm. any chance of a shorter operator, like '#'? I kinda agree that >> hstore_in and the operator don't have to be the same, but requiring >> three letter token for the two most high traffic operations w/hstore >> seems off to me. >> >> # is currently used for bitwise xor/geo > > I'm happy to do whatever the consensus is. I thought it would be > easier to remember if the two operators were spelled at least somewhat > similarly, but I just work here. Perhaps -> Would a colon work? (That's enough bikeshedding for me.) Michael Glaesemann grzm seespotcode net -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |