On Sat, 2024-06-08 at 05:37 +0800, yanliang lei wrote:
> there is the following description in the
> https://www.postgresql.org/docs/current/runtime-config-connection.html：
>
> A value of 0 (the default) selects the operating system's default.
> but there is no description about“ the operating s
thank you very much！
At 2024-06-10 17:03:07, "Laurenz Albe" wrote:
>On Sat, 2024-06-08 at 05:37 +0800, yanliang lei wrote:
>> there is the following description in the
>> https://www.postgresql.org/docs/current/runtime-config-connection.html：
>>
>> A value of 0 (the default) sel
The manual still seems to offer just such a guarantee here:
https://www.postgresql.org/docs/current/sql-select.html#SQL-UNION
> Multiple UNION operators in the same SELECT statement are evaluated left
to right, unless otherwise indicated by parentheses.
In the case of UNION ALL, is this supposed
Hi there,
I mentioned to Jeremy at pgConf.dev that using non-default collations
in some SQL idioms can produce undesired results, and he asked me to
send an email. An example idiom is the way Django implements
case-insensitive comparisons using "upper(x) = upper(y)" [1][2][3] ,
which returns false
