Re: Sugerencia de opcion - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Sugerencia de opcion
Date
Msg-id 603c8f071001240654t11884cc0kae1f0d1907c63e38@mail.gmail.com
Whole thread Raw
In response to Sugerencia de opcion  ("Informatica-Cooperativa Cnel. Oviedo" <informatica@coopovie.com.py>)
Responses Re: [GENERAL] Sugerencia de opcion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2009/1/22 Informatica-Cooperativa Cnel. Oviedo <informatica@coopovie.com.py>:
> Buenos Dias todos,
>
>                             Soy un usuario de postgres de Paraguay, consulto
> sobre la posibilidad de inclucion en la futura version la siguiente
> sentencia(Uso de alias en la condicion HAVING ):
>
>
>     SELECT id, sum(salario) as SumaSalario
>     FROM salarios
>     GROUP BY id
>     HAVING SumaSalario>500;

I've wished for that syntax once or twice myself, but I'm assuming
there's a reason we haven't implemented it?  Part of the problem is
it's inheritantly ambiguous if salarios happens to contain a column
called sumasalario, which is a problem that seems to arise for me
fairly regularly in practice.  Still, it would be nice for WHERE/GROUP
BY/HAVING clauses to have an explicit way to reference "the target
list column called foo".

...Robert

pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: Red-black tree for GIN
Next
From: "Kevin Grittner"
Date:
Subject: Re: commit fests