Re: Order of before_delete trigger in docs

[prev] [thread] [next] [Date index for 2005/06/27]

On Mon, Jun 27, 2005 at 04:34:55AM +0300, Marius Feraru wrote:
> >$role->delete;
> >
> >results in:
> >
> >   PersonRole before_delete
> >   Role before_delete
> 
> This should only happen when you also have a reverse relation like:
>   DB::PersonRole->has_a(role => 'DB::Role', 'id');

Interesting.  Yes, if I manually setup the relationships the Role
trigger is called first.  But, using CDBI::Loader::Pg they are called
in the order above.  I'm not having any luck making the triggers get
called in the reverse order when not using CDBI::Loader, but it's late.

This started by trying to use a trigger to prevent a cascade delete
with:

DB::Role->add_trigger(before_delete => sub {
    my $role = shift;
    die "Can't delete Role ($role) -- In use by one or more Person records\n"
        if DB::PersonRole->search( { role => $role } )->first;
} );


Which doesn't work when I use CDBI::Loader but does otherwise.


        -- 
        Bill Moseley
moseley@xxxx.xxx