Even if the function did a select from d, it could still have plenty of
duplicates. To remove that possibility you would have to use the distinct
clause which is also generally less efficient then a group by.
"Bruno Wolff III" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Sat, F
quot; <[EMAIL PROTECTED]>;
Sent: Saturday, February 19, 2005 13:36
Subject: Re: [GENERAL] Group By and wildcards...
> On Sat, Feb 19, 2005 at 15:59:52 -0200,
> Jon Lapham <[EMAIL PROTECTED]> wrote:
> >
> > Since I do not want to have to re-write all my aggregate fun
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> On Sat, Feb 19, 2005 at 12:07:12 -0200,
> Jon Lapham <[EMAIL PROTECTED]> wrote:
> >
> > SELECT a.*, b.*, c.*, SUM(d.blah)
> > FROM a, b, c, d
> > WHERE
> > GROUP BY a.*, b.*, c.*
> >
> > Instead of having to expand the "GROUP BY a.*, b.*, c.*" usi
On Sat, Feb 19, 2005 at 14:02:34 -0500,
Oisin Glynn <[EMAIL PROTECTED]> wrote:
>
> But the where clause defines the result of the aggregate function (in this
> case the SUM)?
Not really.
> Is the only reason for needing the GROUP BY CLAUSE is because the aggregate
> function demands it?
Note
Jon Lapham wrote:
Ugh.
Since I do not want to have to re-write all my aggregate function
containing queries upon modifications to the table definitions (and I do
not want to write multi-thousand character long SELECT statements),
maybe it is easier to use a temp table intermediary?
Ugly... ugl
On Sat, Feb 19, 2005 at 15:59:52 -0200,
Jon Lapham <[EMAIL PROTECTED]> wrote:
>
> Since I do not want to have to re-write all my aggregate function
> containing queries upon modifications to the table definitions (and I do
> not want to write multi-thousand character long SELECT statements),
Tom Lane wrote:
Bruno Wolff III <[EMAIL PROTECTED]> writes:
Jon Lapham <[EMAIL PROTECTED]> wrote:
When using queries with aggregate functions, is there any way to not
have to have to explicitly write all the columns names after the GROUP
BY ? I would like to use a wildcard "*".
Don't those tab
On Sat, Feb 19, 2005 at 12:40:40 -0500,
Tom Lane <[EMAIL PROTECTED]> wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
> > Jon Lapham <[EMAIL PROTECTED]> wrote:
> >> When using queries with aggregate functions, is there any way to not
> >> have to have to explicitly write all the columns na
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> Jon Lapham <[EMAIL PROTECTED]> wrote:
>> When using queries with aggregate functions, is there any way to not
>> have to have to explicitly write all the columns names after the GROUP
>> BY ? I would like to use a wildcard "*".
> Don't those table
On Sat, Feb 19, 2005 at 12:07:12 -0200,
Jon Lapham <[EMAIL PROTECTED]> wrote:
> When using queries with aggregate functions, is there any way to not
> have to have to explicitly write all the columns names after the GROUP
> BY ? I would like to use a wildcard "*".
>
> Imagine tables a, b, c,
When using queries with aggregate functions, is there any way to not
have to have to explicitly write all the columns names after the GROUP
BY ? I would like to use a wildcard "*".
Imagine tables a, b, c, d each with hundreds of columns.
As an example, I would like to write:
SELECT a.*, b.*, c.
11 matches
Mail list logo
