Thank you very much for your answer, Michael! Yes, what Cheyenne tried to
use was simply not the right grammar.
Thanks,
Maryann
On Mon, Sep 19, 2016 at 10:47 AM, Michael McAllister <
mmcallis...@homeaway.com> wrote:
> This is really an ANSI SQL question. If you use an aggregate function,
>
This is really an ANSI SQL question. If you use an aggregate function, then you
need to specify what columns to group by. Any columns not being referenced in
the aggregate function(s) need to be in the GROUP BY statement.
Michael McAllister
Staff Data Warehouse Engineer | Decision Systems
I was wondering because it seems extra wordy
I'm not an expert in traditional SQL or in Phoenix SQL, but my best guess
is "probably not".
But I'm curious as to why you would like to avoid the group by or the list
of columns. I know it looks very wordy, but are there any technical
reasons? In my experience SQL is hard to read by human eyes
Hi! I think you need something like
group by u.first_name
on the end. Best guess. :)
On Sun, Sep 18, 2016 at 11:03 PM, Cheyenne Forbes <
cheyenne.osanu.for...@gmail.com> wrote:
> this query fails:
>
> SELECT COUNT(fr.friend_1), u.first_name
>>
>> FROM users AS u
>>
>> LEFT
this query fails:
SELECT COUNT(fr.friend_1), u.first_name
>
> FROM users AS u
>
> LEFT JOIN friends AS fr ON u.id = fr.friend_2
>
>
with:
SQLException: ERROR 1018 (42Y27): Aggregate may not contain columns not in
> GROUP BY. U.FIRST_NAME
>
TABLES:
users table with these
