Re: [HACKERS] Bug on complex join
| От | Thomas G. Lockhart |
|---|---|
| Тема | Re: [HACKERS] Bug on complex join |
| Дата | |
| Msg-id | 36DFF31C.1E51F679@alumni.caltech.edu обсуждение исходный текст |
| Ответ на | Bug on complex join (Oleg Broytmann <phd@sun.med.ru>) |
| Ответы |
Re: [HACKERS] Bug on complex join
|
| Список | pgsql-hackers |
> SELECT sh.distr_id , d.distr_id
> FROM central cn, shops sh, districts d
> WHERE cn.shop_id = sh.shop_id
> and got 27963 rows.
> But the query
> SELECT d.*
> FROM central cn, shops sh, districts d
> WHERE cn.shop_id = sh.shop_id AND sh.distr_id = d.distr_id
Why did you change both the target columns *and* the query qualification
between these two examples? Is the "SELECT d.*" required to get the
query to fail?? If not, then...
For some reason sh.distr_id is not equal to d.distr_id. Are they
different data types? Do they have some embedded blanks?? Probably not a
Postgres bug, since the query itself looks pretty simple...
- Tom
В списке pgsql-hackers по дате отправления: