| Subject | Re: [firebird-support] TRIGGER handling differences? (between v1.52 and v1.53) |
|---|---|
| Author | Helen Borrie |
| Post date | 2007-06-15T15:19:18Z |
At 12:41 AM 16/06/2007, you wrote:
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.
There are also enhancements, including a reimplementation of cursors in PSQL.
./heLen
>Hi,There are now stricter common-sense restrictions on what you can
>
>Has anyone come across the above?
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.
There are also enhancements, including a reimplementation of cursors in PSQL.
>If so, any information would be appreciated.Study the release notes.
./heLen