From: | "Ben Tilly" <btilly(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SQL feature requests |
Date: | 2007-08-23 16:57:16 |
Message-ID: | acc274b30708230957w182d5aeqebb819ec7862f598@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/23/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Ben Tilly" <btilly(at)gmail(dot)com> writes:
> > ... But then I need this (possibly
> > empty) list to have a valid group by statement at the end. In Oracle
> > I used to just write it like this:
>
> > SELECT ...
> > GROUP BY $possible_term_1
> > $possible_term_2
> > $possible_term_3
> > 'end of possible groupings'
>
> FWIW, that will work if you write it as
>
> 'end of possible groupings'::text
Ah, that is the solution that I'll move to.
> I'm disinclined to accept it as-is because (a) it's highly likely to be
> a mistake, and (b) there's no principled way to assign a datatype to the
> expression, if we are to interpret it as an expression.
>
> Basically anything but an unadorned constant will work there.
As long as that behaviour is guaranteed, I'm OK on this one.
Ben
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-23 17:08:01 | Re: Undetected corruption of table files |
Previous Message | Alvaro Herrera | 2007-08-23 16:55:07 | Re: SQL feature requests |