Re: Empty SELECT result at simultaneous calls - Mailing list pgsql-general

From Stefan Wild
Subject Re: Empty SELECT result at simultaneous calls
Date
Msg-id 807691.55538.qm@web26707.mail.ukl.yahoo.com
Whole thread Raw
In response to Re: Empty SELECT result at simultaneous calls  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Empty SELECT result at simultaneous calls  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Empty SELECT result at simultaneous calls  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general
Hello,

as already stated: "When I'm working with delays in the servlets, everything works fine." the same selects on the same
idwork fine if delayd. So the data should not be the problem. 

regards, Stefan Wild

--- Tom Lane <tgl@sss.pgh.pa.us> schrieb am Mi, 8.9.2010:

> Von: Tom Lane <tgl@sss.pgh.pa.us>
> Betreff: Re: [GENERAL] Empty SELECT result at simultaneous calls
> An: "Stefan Wild" <wilds81@yahoo.de>
> CC: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
> Datum: Mittwoch, 8. September, 2010 01:27 Uhr
> Stefan Wild <wilds81@yahoo.de>
> writes:
> > I have a problem with my web application and postgres.
> I have several servlets on a page which results in severeal
> simultaneous data base calls kind of:
>
> > SELECT d.id, d.aa, d.ab, ts.ac, d.ad, d.af, d.ag,
> d.ah, d.ai, d.aj, d.ak, d.al, d.am, d.an, d.ao, d.ap, d.ar,
> d.as, d.at, d.au, d.av, d.ax, d.ay, d.az, d.ba, d.bb, d.bc
> FROM c_depots d INNER JOIN c_aa ts ON d.bd_id=ts.id INNER
> JOIN cx_users_depots cx ON cx.id_depots=d.id INNER JOIN
> c_users u ON cx.id_users=u.id WHERE d.id=13
>
> > Even though I have "d.id 13" the SELECT result is
> empty.
>
> Um, well, that's not obviously wrong.  If that d row
> doesn't have join
> partners in all those other tables, you won't get anything
> out of the
> inner joins.  Maybe you want to left-join, instead?
>
>            
> regards, tom lane
>




pgsql-general by date:

Previous
From: Sam Mason
Date:
Subject: Re: joins with text search
Next
From: Alvaro Herrera
Date:
Subject: Re: Empty SELECT result at simultaneous calls