Re: Lets prohibit predicting the future in the documentation.
On Mon, Aug 4, 2025 at 12:30 PM David G. Johnston wrote: > I’m not saying it is wrong because it is impossible this will ever be > implemented. It’s wrong because after 7 years the probability of this being > removed are somewhere near 5% which is “unlikely”. Had it been truly likely > it would have been done within a few years at worse, IMO. I have mixed feelings about this particular example, but I agree that it's best not to prognosticate about future feature development in the docs, or even future deprecation. We're wrong A LOT when we do that. It's best to just document what is and not what might be later. -- Robert Haas EDB: http://www.enterprisedb.com
Re: SELECT List with/without parentheses
On 06/09/2025 02:02, Jason Tiller wrote: Thanks for your feedback! I'm a SQL newbie and the "implicit row constructor" syntax was an unwelcome surprise. The reason for it is so you can write WHERE (a, b) > (1, 2) and similar. Perhaps WHERE ROW(a, b) > ROW(1, 2) would have been better, perhaps not. -- Vik Fearing
