Hi,

>
> > If I recall correctly, there was a change in Firebird
> supporting wild-
> > card events, is that right?
>
> Partially. I'm the one who's responsible for this piece of
> code. The work is
> 95% done, but there is still a couple of pending issues to be
> solved, so the
> code hasn't been commited to the CVS tree yet. I'm going to
> complete it for
> v1.5.

? Will there be a 1.5 version ? That's kinda new to me :)

> > If so, how does one register for such events? Just like the old way
> > and the engine will handle the actual posting?
> >
> > eg:
> >
> > register: uren.update.*
> >
> > post-event:
> > uren.update.10
> > uren.update.test
> > uren.update.xx
>
> Yes, the registration is fully compatible with the current design. The
> engine compares the actually posted events with the
> registered masks and
> delivers the actual events to all requesters.

Just what I expected :)

> With wildcarded events isc_event_counts() will return the summarized
> information:
>
> uren.update.* = 7
>
> and new API call (let's name it isc_event_details) will
> return something
> like this:
>
> uren.update.10 = 2
> uren.update.test = 1
> uren.update.xx = 4

Ah, ok - that makes sense.

> Since I haven't implemented this API routine yet, you're
> welcome to discuss
> it in the firebird-devel mailing list to find the most
> appropriate solution
> together.

I'm not very much into the API and all. But I can discuss from a technical
developer point of view.

> Please also note that this feature will be immediately
> available only with
> API level programming. AFAIR, Jason has shown an interest in
> supporting this

Very good - I'm using IBO most of the time :)

> in IBO, but I'm afraid IBX users will never be able to use such an
> improvement until we decide to provide a patch for every IBX
> update released
> by Jeff.

IBX will be a problem indeed. Perhaps someone can take the time to transform
IBX into FBX? (sorry, I don't)


I'll be monitoring firebird-devel for any threads about the issue...


Martijn Tonies



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