> On 28.05.2020, at 23:43, Tom Lane wrote:
>
> Markus Winand writes:
>> However, if the conflict happens in a subquery, it doesn’t anymore:
>
>>WITH data (c, posix) AS (
>>values ('a' COLLATE "C", 'b' COLLATE "POSIX")
>>)
>>SELECT *
>> FROM (S
Markus Winand writes:
> However, if the conflict happens in a subquery, it doesn’t anymore:
> WITH data (c, posix) AS (
> values ('a' COLLATE "C", 'b' COLLATE "POSIX")
> )
> SELECT *
> FROM (SELECT *, c || posix AS none FROM data) data
>
Hi!
I think I’ve found a bug related to the strength of collations. Attached is a
WIP patch, that address some other issues too.
In this this example, the conflict of implicit collations propagates correctly:
WITH data (c, posix) AS (
values ('a' COLLATE "C", 'b' COLLATE
