Subject | Re: [Firebird-Architect] MVCC + a day in life the mysql instructor |
---|---|
Author | Jim Starkey |
Post date | 2009-03-13T18:57:53Z |
Ann W. Harrison wrote:
trigger per operation type per table. I didn't have the foggiest idea
of how popular triggers would be, and how much of a pain in the butt
combining a bunch of independent triggers into a single one would be.
Version 2.0 supported multiple triggers per operation per table with a
sequence number to determine firing order.
Something that I've learned over the ages is that users will always
surprise me.
--
Jim Starkey
President, NimbusDB, Inc.
978 526-1376
> marius adrian popa wrote:Not quite. gds/Galaxy 1.0 (later renamed Interbase) has a single
>
>
>> The other day some book recommends (weird sybase consultant) to avoid
>> Triggers ,
>> I don't know for me in interbase/firebird seems natural to use them
>> and i didn't have any issues with them
>> I fact i can't imagine life without triggers or views or transactions.
>> Anyone knows when they were introduced in interbase?
>>
>
> Triggers, views, and transactions were part of InterBase V1.0 - circa
> 1985. Views did not include group by or outer joins. From the start
> InterBase had multiple triggers per time/action (e.g before insert)
> and a sequence number to order them.
>
>
trigger per operation type per table. I didn't have the foggiest idea
of how popular triggers would be, and how much of a pain in the butt
combining a bunch of independent triggers into a single one would be.
Version 2.0 supported multiple triggers per operation per table with a
sequence number to determine firing order.
Something that I've learned over the ages is that users will always
surprise me.
--
Jim Starkey
President, NimbusDB, Inc.
978 526-1376