Subject Re: [Firebird-Architect] Another Model for Database Events
Author Jim Starkey
Martijn Tonies wrote:
>> The key difference between NimbusDB and Firebird events is that NimbusDB
>> events carry before and after data while Firebird events are just
>> "something happened".
> So then it's not really "another model" but rather a slightly different
> beast by the
> same name, right?
> NimbusDB events are some sort of triggers that raise a signal back to the
> client?
It really is a different model in that it returns data with the event
rather than just signaling that the event occurred. The resource
consumption is higher for NimbusDB events that Firebird events, but
memory and cycles are lot cheaper than they used to be.

NimbusDB events are generated by the update code rather than triggers.
As I said before, the event mechanism is general, but at the moment, the
only type of events are record update events.

Jim Starkey
Founder, NimbusDB, Inc.
978 526-1376

[Non-text portions of this message have been removed]