Muris Pucic wrote:
> -- The query below works, even though there is no column "first_name" in
> TABLE2. This should return an error but it does not, it returns all rows
> from TABLE1. This query should not evaluate correctly even when aliases are
> not used because it can be misleading.
>
> SELEC
"Muris Pucic" writes:
> -- The query below works, even though there is no column "first_name" in
> TABLE2. This should return an error but it does not, it returns all rows
> from TABLE1. This query should not evaluate correctly even when aliases are
> not used because it can be misleading.
> SELE
Muris Pucic wrote:
> -- The query below works, even though there is no column "first_name" in
> TABLE2. This should return an error but it does not, it returns all rows
> from TABLE1. This query should not evaluate correctly even when aliases are
> not used because it can be misleading.
>
> SELECT
The following bug has been logged online:
Bug reference: 5122
Logged by: Muris Pucic
Email address: t...@multicom.ba
PostgreSQL version: 8.2
Operating system: Vista
Description:Subqueries - inner select statement bug
Details:
Hi,
If we have two simple tables:
TABL
