Re: ERROR: More than one tuple returned by a subselect used as an expression. - Mailing list pgsql-novice

From Josh Berkus
Subject Re: ERROR: More than one tuple returned by a subselect used as an expression.
Date
Msg-id 200304031655.31704.josh@agliodbs.com
Whole thread Raw
In response to Re: ERROR: More than one tuple returned by a subselect used as an expression.  ("Mel Jamero" <mel@gmanmi.tv>)
List pgsql-novice
Mel,

> Thanks a lot Josh!!

You're welcome.

> I wasn't thinking too hard..
>
> but then again the 2nd option (UPDATE..SET..FROM) you gave is really
> something new to me. =)

Unlike *some* databases, PostgreSQL supports sub-selects just about anywhere;
in the SELECT, FROM, WHERE, and/or HAVING clauses.  I recommend buying a good
advanced SQL book to give you and idea of the possibilities, such as Joe
Celko's "SQL for Smarties, 2nd Ed.".


--
-Josh Berkus
 Aglio Database Solutions
 San Francisco


pgsql-novice by date:

Previous
From: Josh Berkus
Date:
Subject: Re: question about auto increment like
Next
From: Don Patou
Date:
Subject: configuring postgresql on the browser