Re: mysterious behaviour where = (SELECT JAHR ...
From: Kay Kanekowski <kay.kanekowski_at_web.de>
Date: Mon, 27 Sep 2010 10:00:02 +0200
Message-ID: <i7piu3$n3a$02$1_at_news.t-online.com>
Am 25.09.2010 16:00, schrieb Mark D Powell:
> On Sep 24, 7:17 am, Kay Kanekowski<kay.kanekow..._at_web.de> wrote:
>>
>> works as designed ... but not as expected ;-)
>>
>
> Actually this should not be unexpected behavior since the SQL manual
> explicitly states this requirement: "If columns in a subquery have the
> same name as columns in the containing statement, then you must prefix
> any reference to the column of the table from the containing statement
> with the table name or alias. To make your statements easier to read,
> always qualify the columns in a subquery with the name or alias of the
> table, view, or materialized view."
>
> Reference: OracleŽ Database SQL Reference 10g Release 2 (10.2) Part
> Number B14200-02 section Using Subqueries
>
> HTH -- Mark D Powell --
Date: Mon, 27 Sep 2010 10:00:02 +0200
Message-ID: <i7piu3$n3a$02$1_at_news.t-online.com>
Am 25.09.2010 16:00, schrieb Mark D Powell:
> On Sep 24, 7:17 am, Kay Kanekowski<kay.kanekow..._at_web.de> wrote:
>>
>> works as designed ... but not as expected ;-)
>>
>
> Actually this should not be unexpected behavior since the SQL manual
> explicitly states this requirement: "If columns in a subquery have the
> same name as columns in the containing statement, then you must prefix
> any reference to the column of the table from the containing statement
> with the table name or alias. To make your statements easier to read,
> always qualify the columns in a subquery with the name or alias of the
> table, view, or materialized view."
>
> Reference: OracleŽ Database SQL Reference 10g Release 2 (10.2) Part
> Number B14200-02 section Using Subqueries
>
> HTH -- Mark D Powell --
ok, i correct it:
works as designed ... but not as Norbert and i expect it ;-)
regards
Kay
Received on Mon Sep 27 2010 - 03:00:02 CDT