Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Q: columns seen in triggers
On Aug 1, 7:27 pm, yf..._at_vtn1.victoria.tc.ca (Malcolm Dew-Jones)
wrote:
> I know from experience that at least in
>
> Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
>
> if a column is not included in an update statement and an update trigger
> sets the value of the column then the value provided by the trigger is not
> saved.
> For the column value assigned by the trigger to be saved, the update has
> to include the column in the list of columns being set.
What - where did you get this ?
I usually use triggers to set the "last modified user" and "last
modified datetime" data
and they are never referrence in the update statement.
> HOWEVER, I also know that the above is not always true. For example the
> query I am just looking at does not mention the WHEN_UPDATED column, but
> the value set by the trigger _is_ saved.
As D.A. Morgan indicated, if you have any occurance of this mysterious
behavior happening,
please provide the test case material - it would be an intering bug...
> I wonder where the exact details of what is going on is documented.
> If someone could enlighten me I would appreciate it, thanks.
All Oracle documentation is available online, free at
tahiti.oracle.com
or google "Oracle triggers" and you should find tons.
hth Received on Sun Aug 05 2007 - 22:25:22 CDT
![]() |
![]() |