> >Whilst debugging my app, I noticed that Firebird v1.52 SS kept
> >abnormally terminating. I tracked it down to a recent trigger I'd

added:

> >
> >CREATE TRIGGER CONTACTS_CHANGED FOR CONTACTS ACTIVE AFTER INSERT OR
> >UPDATE OR DELETE POSITION 1 AS
> >begin
> > POST_EVENT 'CONTACT_CHANGED_' || old.contact_id;
> >end
> >
> >Everytime
>
> == or just after inserts?

Yes, just inserts

> What's the data type of contact_id? Is it potentially longer than 62

bytes?

It's an Integer.

> POST_EVENT obviously isn't a lot of use if you make up its string
> on the fly. The idea of events is for client apps to *know* what

the event

> identifiers are and to listen for them.

Any client looking at that contact will be listening for this
particular event. No doubt you'll tell me I shouldn't be doing that
and should do it another way (I'm willing to be educated) , but it's
worked well thus far.

> Your attempt to "enhance" the
> event by adding run-time data to it should be trapped somehow (but
> apparently isn't), even if it is just swallowed.

Clients could listen for that enahnced event.

> No exception should crash the server. Please prepare a reproducible

test

> case and offer it initially in firebird-devel. Make sure you are

explicit

> about the version[s] of both server and client that were involved.

Will do. In fact, using Database Workbench, I've just created a
similar trigger on another table and inserted a row = bang, server
terminated (v1.52 final).

Thanks.