Ann W. Harrison wrote:

>Andrea,
>
>
>
>>I'm facing a quite serious problem. Please tell me whether I'm doing
>>something wrong or I've found a bug.
>>
>>
>
>One thing I can tell you for sure is that you've missed a feature.
>Firebird allows you to define multiple triggers and specify the order of
>firing and the operation on which they will be fired. The reason for
>allowing multiple triggers is to avoid piles of spaghetti code and
>sequences of unrelated actions - each trigger performs a specific
>operation and can be deactivated for testing.
>
>

That's a good point, probably a suggestion to keep in mind in the future :)

Anyway, it's not the trigger which I'm really using. The original
trigger executes some stored procedures which contains different steps
of that code. I've merged anything in a single trigger (which obviously
has the same problem as the original one) since I thought that it would
be easier for you to understand what the trigger does...

>As a general thing, using double quotes on object names is a waste of
>time. If you need to use a reserved word as a column or table or
>procedure or view name, OK, that's a good reasons. If you need to use a
>name with a space or a non-ascii character, OK, that's a good reason.
>If you like typing double quotes everywhere, that's a reason but not one
>that's going to please many of us who answer questions on this list.
>
>

I like delimited identifiers because I'm used to the Pascal case
notation when I work on the business tier (Java, C#, C++...) and I do
not really like to use underscores... even if it is quite standard for
database designers. But that's obviously a problem of personal taste.

>When I finish disentangling your trigger, I'll try to have a better answer.
>
>

Thank you very much! What seems strange to me is that it works correctly
when updating a single row...

Best regards, Andrea

--
Andrea Sansottera
UGIdotNET [Italian] http://www.ugidotnet.org
My weblog [Italian] http://blogs.ugidotnet.org/andrew/