Exactly right. In general you should never let ERwin write your triggers.
If you want triggers, write your own, although as Marc said foreign keys and
other constraints are a much better idea in Oracle.
"Marc Blum" <marc_at_marcblum.de> wrote in message
news:1103_1002556708_at_pc-marcblum...
> On 8 Oct 2001 06:27:19 -0700, in comp.databases.oracle.server you wrote:
> > Yet another problem in moving from another DBMS to Oracle 8.1.7:
> >
> > The schema for a DB which is being moved to Oracle, as an example, has
> > two tables A and B. A is B's parent and B is A's child. ERWin has
> > generated triggers to support Referential Integrity (A-Cascade Update,
> > B-Update Restrict), and at the moment of UPTATE of a record in table A
> > (parent) Oracle throws "Mutating table" error.
> >
> > Oracle has published "Avoiding Mutating Tables" article
> > (http://osi.oracle.com/~tkyte/Mutate/index.html) concerning that
> > question, but the solution is cumbersome.
> >
> > The questions:
> > 1) Does anybody know if that problem has been solved in Designer/2000
> > by Oracle or PowerDesigner by Sybase ?
> > 2) Has anyone an experience in writing custom ERWin trigger templates
> > resolving that problem ?
> >
> > Best Regards,
> >
> > Aleksey Burdakov
> >
> > P.S. I am talking of the both ERWin 3.5.2 and 4.0 with the latest SPs.
>
> Just disable ERwin-generated Triggers and rely on declarative
RI-Constraints
>
> Marc
>
>
Received on Mon Oct 08 2001 - 18:50:05 CDT
