On Feb 3, 2008 5:07 PM, Grzegorz Nosek <[EMAIL PROTECTED]> wrote:
>         ->meta->column('is_even')
>         ->add_trigger('on_set',
>         sub {
>                 unset_column_value_modified( $_[0], 'is_even' )
>         });
> R::DB::O::Util is imported earlier with :columns
> But unfortunately, no go (no observable change in behaviour). Is this the
> right way to set up the trigger? After sticking a die in the callback
> the code survived too.

Sorry, actually I should have suggested on_load, but no matter because
something else is obviously wrong.  Can you post a small
self-contained example including the table definitions and class
definitions?  That's usually the fastest way to get to the bottom of
these things.

> BTW, below is the patch I'm using. If you could have a look at it and
> check for obvious blunders, I'd be very grateful. I'm including it for
> the off chance that I broke something by using it.

That's another thing: why is the table prefix necessary even on
single-table queries?  I suspect the aforementioned self-contained
example will illuminate this as well, once I try to run it.

As for the patch, it looks reasonable but I'd rather understand why
it's necessary and provide official support for it than encourage you
to continue using your patch :)


This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Rose-db-object mailing list

Reply via email to