On Thu, Mar 29, 2001 at 01:35:54PM -0600, elble@stripped wrote:
> > We were thinking something like:
> > "Gee, you can add UDFs to MySQL today by building an .so and telling
> > MySQL to use it. Then it's available for queries. What if we did
> > something similar that allowed a user to write `triggers' that could
> > do fairly simple things on the server side."
> > The specific thing we wanted initially was the ability for the server
> > to send a multicast message when a particular update happened.
> yah, i think we're all on the same wavelength here...
Unless somebody steps forward with an existing implementation or shoots
down the approach/suggests a better one, I'll probably start on the
trigger classes early next week. The big hurdle for me is learning how
to unpack records into List<Item> containers (since update triggers need
pre and post, otherwise all triggers could work like Procedures do and
just accept fields).
'course, since *I* don't need the old_rec, I guess I could hack it in
to just pass "fields". But I'd like to do the right thing(tm) here.