MIME-Version: 1.0
References: <557588747.121401914.1746016151124.JavaMail.zimbra@meteo.fr>
In-Reply-To: <557588747.121401914.1746016151124.JavaMail.zimbra@meteo.fr>
From: David Rowley <dgrowleyml@gmail.com>
Date: Thu, 1 May 2025 01:09:05 +1200
Message-ID: <CAApHDvpxHjkguu2zs3Fv2okrgvKzT27ao5CXfyVn7xhXc5HWLw@mail.gmail.com>
Subject: Re: SQL ERROR subquery uses ungrouped column in PostgreSQL
To: PALAYRET Jacques <jacques.palayret@meteo.fr>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CAApHDvpxHjkguu2zs3Fv2okrgvKzT27ao5CXfyVn7xhXc5HWLw%40mail.gmail.com>
Precedence: bulk

On Thu, 1 May 2025 at 00:29, PALAYRET Jacques <jacques.palayret@meteo.fr> wrote:
> => In the subquery, the semantic analysis of the query considers the column " dat " instead of the expression " to_char(dat,'yyyymm') ", which is actually a grouped column.
> Is this normal? How can I simply resolve the problem?

Calculate the dat column in a subquery in the outer-level query.

Something like:

FROM (select *,to_char(dat, 'YYYYMM') as strdat from table1) table1
JOIN   table2   USING (num_poste)

then use strdat in all the places you're currently using to_char(dat, 'YYYYMM')

David