Re: Putting an aggregate value in an UPDATE statement...

From: Leif Biberg Kristensen <leif(at)solumslekt(dot)org>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: Putting an aggregate value in an UPDATE statement...
Date: 2010-06-01 21:26:05
Message-ID: 201006012326.05068.leif@solumslekt.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

> You need them to syntactically separate the sub-select from the outer
> select. If SQL didn't require them, then in something like
>
> UPDATE question_choices SET total_rows =
> select count(*) from care_lesson where something
>
> it wouldn't be clear whether the WHERE clause was meant to attach
> to the sub-select or the outer UPDATE.

A couple of days ago, a was a little stumped by this. I had written a plain
SQL function with one integer parameter, and then tried to use a SELECT as
input parameter as in

SELECT myfunc(SELECT foo FROM bar WHERE baz);

It took a while before I realized that I needed to put the query in another
set of parentheses:

SELECT myfunc((SELECT foo FROM bar WHERE baz));

worked just fine. I fail to see the ambiguity here, though.

regards,
--
Leif Biberg Kristensen
http://solumslekt.org/blog/

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2010-06-01 21:34:39 Re: Putting an aggregate value in an UPDATE statement...
Previous Message Tom Lane 2010-06-01 21:15:52 Re: Putting an aggregate value in an UPDATE statement...