Subject | Re: [IB-Architect] UDF replacement: native shared libraries vs. Java |
---|---|
Author | Ann Harrison |
Post date | 2000-04-16T18:10Z |
At 11:39 PM 4/6/00 -0600, Tim Uckun wrote:
especially if you're comparing it with a built-in trigger that's inserting
the current data into a row. There's also a lot of information available
to stored procedures and triggers (connection, transaction, current row,
new row, parameters...)
The language neutral part is very attractive though...
Ann
>Just thinking out loud here...Ummm... Switching process context tends not to be simple or light -
>
>What if instead of having triggers and stored procedures the database could
>send events or signals. that way your code could hook into the database
>events yet be running outside the database altogether. Of course this could
>also be completely language neutral so you could code in PERL if you wanted
>to..
>
>Leave the database engine light and simple.
especially if you're comparing it with a built-in trigger that's inserting
the current data into a row. There's also a lot of information available
to stored procedures and triggers (connection, transaction, current row,
new row, parameters...)
The language neutral part is very attractive though...
Ann