Re: update statement PL/SQL

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Thu, 28 Apr 2005 13:17:00 -0700
Message-ID: <1114719185.116475@yasure>

pobox002_at_bebub.com wrote:

> DA Morgan wrote:
>
>

>>How did you figure all of this out from the OP's original post?
>>
>>Here is what the OP wrote:
>>"I try to update data from 1 table from another table."
>>
>>All the materialized views on the planet will not update a table.

>
>
> Because I read the full post including the sentence after your
> selective quote.
>
>

>>>>>I'm a newbie here.  I try to update data from 1 table from another
>>>>>table.  So I used cursor to update my employee table on Total_sale
>>>>>column  = amount column on Sales Table where employee.empid =
>>>>>sales.empid.

>
>
> I will admit I assumed a one to many relationship from employee to
> sales to lead me to the materialized view suggestion, and the answer to
> the update question which I also provided having an an aggregate
> function.
>
> I am not suggesting that a materialized view be used to update a table.
> I am suggesting the materialized view be used instead of updating a
> table.

Not to prolong this ... I too read that he used a cursor. I also thought to myself ... "Why?" As it turns out the cursor had no purpose. Not a big stretch as there is almost no justification, in Oracle, to ever use a cursor.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)

Received on Thu Apr 28 2005 - 15:17:00 CDT