Subject Re: TRIGGER handling differences? (between v1.52 and v1.53)
Author Adam
--- In, Helen Borrie <helebor@...> wrote:
> At 12:41 AM 16/06/2007, you wrote:
> >Hi,
> >
> >Has anyone come across the above?
> There are now stricter common-sense restrictions on what you can
> assign to in triggers...a few nonsensical assignments that were no-op
> previously now throw exceptions. For example, you will get a "Cannot
> update read-only...." exception (I forget the actual words) if you
> have an after trigger that tries to assign a value to a NEW variable.


I thought that 1.5.3 was just a bug-fix release, so I would be
surprised if there were any differences.

Your comments are definitely relevant for a 1.5.x to 2.x upgrade.


PS + off topic: Hopefully this weather will miss you guys.