From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: syntax pb |
Date: | 2023-05-30 15:57:59 |
Message-ID: | ZHYdB2bsrd9kL2d+@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 30, 2023 at 05:53:30PM +0200, Marc Millas wrote:
> Thanks Adrian, but if the query becomes more complex, for example with a
> few joins more, then even casting doesn't work.
> This comes from a prod environment and even casting NULLs (which is more
> than strange, BTW) generates absurd errors.
> Too my understanding it looks like the parser did not parse the select
> distinct as we think he does.
Show *real* example that doesn't work, with schema. Clearly your example
can be easily made to work.
Best regards,
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Carsten Klein | 2023-05-30 17:04:20 | File-Access functions by default not executable by predefined role "pg_read_server_files" |
Previous Message | Marc Millas | 2023-05-30 15:53:30 | Re: syntax pb |