Re: problems with updates

The way to get around the mutating table error is to have the trigger fire on a view. The view is merely a SELECT * FROM original_table. Your trigger body would include this:

UPDATE trick_view
SET date_col=sysdate
WHERE :old.pk_col=trick_view.pk_col;

Works like a charm.

Andrew

bryan munday wrote in message <3B03A84E_at_MailAndNews.com>...
>The date needs to be on the row that is being updated
>
>Thanks
>
>Bryan
>
>>===== Original Message From Galen Boyer <galenboyer_at_yahoo.com> =====
>>On Tue, 8 May 2001, bardy_at_MailAndNews.com wrote:
>>
>>> It is important that the date is kept on the table itself if at
>>> all possible.
>>
>>Do you need to maintain an updated date on the row that is
>>currently being updated or do you need to update a row that is
>>different than the row currently being updated?
>>--
>>Galen
>>I don't want to be the rock. Yeah, okay, what do you want to be?
>>I want to be the piece of glass.
>
>------------------------------------------------------------
> Get your FREE web-based e-mail and newsgroup access at:
> http://MailAndNews.com
>
> Create a new mailbox, or access your existing IMAP4 or
> POP3 mailbox from anywhere with just a web browser.
>------------------------------------------------------------
>
Received on Tue May 08 2001 - 10:24:10 CDT