Quick poll: should @PostgreSQL remove support for postfix operators in expressions, or keep them? Their existence makes parsing a lot harder.
-
-
Replying to @RhodiumToad @PostgreSQL
Perhaps list the ones we currently have?
1 reply 0 retweets 0 likes -
Replying to @AndresFreundTec @PostgreSQL
"ones"? The only one that exists in core+contrib is the ! factorial operator.
2 replies 0 retweets 3 likes -
in which case the question should have been should we remove the one we have. Much easier answer for me anyway.
1 reply 0 retweets 0 likes -
Well there's also the issue that people can define new ones with CREATE OPERATOR; that option would be removed too.
1 reply 0 retweets 1 like -
Ok so when you say harder. What does this mean? Does it equate to a meaningful performance penalty ? Does having it make it impossible to add something else we might want ?
2 replies 0 retweets 0 likes
Having postfix operators forces us to put various subtle hacks in the parser. These then occasionally bite back either when trying to add new syntax or for edge cases of existing syntax. e.g. select 'a' || escape || 'b' from (values ('\')) v(escape);
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.