Re: column update order

From: What's in a namespace <xml_at_ns.com>
Date: Tue, 21 Nov 2006 13:57:35 +0100
Message-ID: <4562f7c0$0$325$e4fe514c@news.xs4all.nl>

"Charles Hooper" <hooperc2000_at_yahoo.com> schreef in bericht news:1164111394.448745.107390_at_h48g2000cwc.googlegroups.com...
> What's in a namespace wrote:

>> "Charles Hooper" <hooperc2000_at_yahoo.com> schreef in bericht
>> news:1164081790.296669.285220_at_f16g2000cwb.googlegroups.com...
>> > Charles Hooper wrote:
>> >> An individual UPDATE, INSERT, or DELETE will be consistent as of the
>> >> time the DDL begins, as will a SELECT.  Additionally, within a
>> >> transaction, all SELECTs, UPDATEs, INSERTs, and DELETEs will be
>> >> consistent as of the start of the transaction.
>> >>
>> >> Charles Hooper
>> >> PC Support Specialist
>> >> K&M Machine-Fabricating, Inc.
>> >
>> > Should state DML (manipulation) not DDL (definition), in case that
>> > causes any confusion.  DDL causes an implicit COMMIT.
>> >
>> > Charles Hooper
>> > PC Support Specialist
>> > K&M Machine-Fabricating, Inc.
>> >
>>
>> Charles,
>>
>> I may have overlooked something, but I still don't understand why the 
>> column
>> OLD_DATE is filled with sysdate in the first example, and filled 
>> correctly
>> in the second example, for in both cases you did:
>>
>> UPDATE
>>   T4
>> SET
>>   O_DATE=C_DATE,
>>   C_DATE=TRUNC(SYSDATE);
>>
>> Thanks,
>>
>> Shakespeare
>

> This does not work as expected:
> UPDATE
> T4
> SET
> OLD_DATE=CURRENT_DATE,
> CURRENT_DATE=TRUNC(SYSDATE);

>

> This _does_ work as expected:
> UPDATE
> T4
> SET
> OLD_DATE=T4.CURRENT_DATE,
> CURRENT_DATE=TRUNC(SYSDATE);

>

> SELECT
> *
> FROM
> V$RESERVED_WORDS
> WHERE
> KEYWORD='CURRENT_DATE';

>


> KEYWORD                RESERVED

> CURRENT_DATE        N

>

> Charles Hooper
> PC Support Specialist
> K&M Machine-Fabricating, Inc.

>

AAARGH, reserved words again. I can hear DA Morgan laughing from here..........

Shakespeare
(what's in a reserved name?) Received on Tue Nov 21 2006 - 06:57:35 CST