Re: Building a "complex" select? - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Building a "complex" select?
Date
Msg-id 1113843499.20921.508.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: Building a "complex" select?  (Bjørn T Johansen <btj@havleik.no>)
Responses Re: Building a "complex" select?  (Bjørn T Johansen <btj@havleik.no>)
Re: Building a "complex" select?  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-general
Then maybe:

AND (log_stop.stoptype=1 OR log_stop.stoptype IS NULL)

??

On Mon, 2005-04-18 at 11:55, Bjørn T Johansen wrote:
> Nope... It returns 0 rows when there are no rows in log_stop with stoptype = 1...
>
> BTJ
>
> Scott Marlowe wrote:
> > On Mon, 2005-04-18 at 11:24, Bjørn T Johansen wrote:
> >
> >>I need a select like this..:
> >>
> >>select ordre.id, ordre.desc, log_stop.stoptype from ordre left outer join log_stop on
> >>ordre.id = log_stop.ordreid where ordre.id = 22
> >>
> >>The problem is that I need to include "where log_stop.stoptype = 1". So if log_stop
> >>includes 3 rows with stoptype = 1 and ordreid = 22, my select should return 3 rows.
> >>Also, if log_stop includes 3 rows with stoptype = 1 and 2 rows with stoptype = 2, my
> >>select should still return 3 rows. And if there are 0 rows with stoptype = 1, my
> >>select should return 1 row.
> >
> >
> > Would this work?
> >
> > select ordre.id, ordre.desc, log_stop.stoptype from ordre left outer join log_stop on
> > ordre.id = log_stop.ordreid where ordre.id = 22 AND COALESCE(log_stop.stoptype,1)=1
> >
> >

pgsql-general by date:

Previous
From: Bjørn T Johansen
Date:
Subject: Re: Building a "complex" select?
Next
From: Alex
Date:
Subject: Help with a plperl function