hstore ==> and deprecate =>
in [PgSql]
|
From: "David E. Wheeler" on 9 Jun 2010 13:41 On Jun 9, 2010, at 10:33 AM, Robert Haas wrote: > Well, that doesn't look much like an arrow, at least not to me... It's a pointer, though. Not in the C sense, of course. But I often use » for "read more" style links in HTML. Its the same idea: move from this to that. Anyway, for comparison's purpose: 'foo' ==> 'bar' 'foo' >> 'bar' Pity 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: "David E. Wheeler" on 9 Jun 2010 12:54 On Jun 9, 2010, at 9:30 AM, Tom Lane wrote: > Andrew Gierth <andrew(a)tao11.riddles.org.uk> writes: >> I'd really like to find a better operator name than ==>. But I'm not >> convinced one exists. > > I agree. +1 No one liked my suggestion of ~> ? Too similar to -> ? Other ideas: 'foo' :> 'bar' 'foo' @> 'bar' 'foo' #> 'bar' 'foo' &> 'bar' 'foo' *> 'bar' 'foo' +> 'bar' 'foo' > 'bar' 'bar' <= 'foo' I actually like :> pretty well. It looks more like =>, and has nice correspondence to := for named function params. Hey, why not Unicode? 'bar' ➡ 'foo' ;-) > Perhaps it would be sane to make hstore_in accept either => or ==>, but > not change hstore_out (for now)? +1 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: Robert Haas on 9 Jun 2010 13:33 On Wed, Jun 9, 2010 at 1:15 PM, David E. Wheeler <david(a)kineticode.com> wrote: > On Jun 9, 2010, at 10:04 AM, Tom Lane wrote: > >>> I actually like :> pretty well. It looks more like =>, and has nice correspondence to := for named function params. >> >> Colon was removed from the set of allowed operator-name characters years >> ago. �There are conflicts with various usages (ecpg & psql variables). >> This is actually a place where the current := behavior could cause some >> issues, though I'm not aware of any at the moment. > > Oh, that's a shame. > > In that case, how about: > > �'foo' >> 'bar' Well, that doesn't look much like an arrow, at least not to me... -- 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: Andrew Gierth on 9 Jun 2010 14:29 >>>>> "Tom" == Tom Lane <tgl(a)sss.pgh.pa.us> writes: >> While I don't like the inconsistency between ==> or whatever and >> the use of => in type input and output, I regard the text >> representation as being much harder to change safely, since client >> code will be parsing it. In this case the inconsistency seems like >> a much smaller problem than changing the text representation. Tom> Perhaps it would be sane to make hstore_in accept either => or Tom> ==>, but not change hstore_out (for now)? I'd be happy with that. -- Andrew (irc:RhodiumToad) -- 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: Merlin Moncure on 9 Jun 2010 15:22
On Wed, Jun 9, 2010 at 1:15 PM, David E. Wheeler <david(a)kineticode.com> wrote: > On Jun 9, 2010, at 10:04 AM, Tom Lane wrote: > >>> I actually like :> pretty well. It looks more like =>, and has nice correspondence to := for named function params. >> >> Colon was removed from the set of allowed operator-name characters years >> ago. �There are conflicts with various usages (ecpg & psql variables). >> This is actually a place where the current := behavior could cause some >> issues, though I'm not aware of any at the moment. > > Oh, that's a shame. > > In that case, how about: > > �'foo' >> 'bar' +1 merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |