Re: Further issues with jsonb semantics, documentation

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Further issues with jsonb semantics, documentation
Date: 2015-06-06 13:15:59
Message-ID: 5572F28F.60908@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 06/05/2015 04:48 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Yeah, Good point. Actually, if my memory serves me correctly (always a
>> dubious bet), the avoidance of that kind of ambiguity is why we
>> introduced the #> and #>> operators in the first place, after going
>> round and round for a while on what the API would look like. I should
>> have remembered that when this came around. Mea culpa.
>> So probably the least invasive change would be to rename the text[]
>> variant operator to something like "#-" and rename the corresponding
>> function to jsonb_delete_path.
> Not sure that's a great choice of operator name; consider for example
> select 4#-1;
> It's not immediately obvious whether the "-" is meant as a separate
> unary minus. There are heuristics in the lexer that try to deal with
> cases like this, but it doesn't seem like a good plan to double down
> on such heuristics always doing the right thing.
>
>

Perhaps we should deprectae operator names ending in "-"?

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-06-06 14:33:26 Re: [CORE] Restore-reliability mode
Previous Message Sehrope Sarkuni 2015-06-06 12:41:13 Re: [CORE] Restore-reliability mode