Subject | Re: Help with a trigger/procedure |
---|---|
Author | Adam |
Post date | 2006-07-28T12:40:29Z |
--- In firebird-support@yahoogroups.com, "Fabio Gomes" <fabioxgn@...>
wrote:
consolidated in another table, but your explanation is far from clear
which is why no specific suggestions have been made. This totalling
means that two inserts may need to update a single record in the other
table.
Perhaps you can simplify your explanation a little, giving an example
of the tables and what you want your trigger to do.
Adam
wrote:
>same table
> Hum, so the main problem would be inserting the same value in the
> at same time?table
>
> Thinking about it, i think i can insert the new value in the table if it
> doesnt exist and then always update it in the trigger event, so i can
> always, insert the new value, commit imediatelly and after that start my
> transaction.
>
> Would it be better?
>
> The method about using the table would work too, off course i have a
> with all the individual item values, but i like to keep that just fortotal
> reports and in case of something goes wrong and i have to recalc the
> stock of an item... i think it would be better to avoid that, i m afraidFrom what you have explained, you have a table that has some totals
> this can slow down everything after i have too many rows there.
>
> Anyway, i m newbie so am open to any suggestions.
consolidated in another table, but your explanation is far from clear
which is why no specific suggestions have been made. This totalling
means that two inserts may need to update a single record in the other
table.
Perhaps you can simplify your explanation a little, giving an example
of the tables and what you want your trigger to do.
Adam