[firebird-support] Re: Cross database update

2014-11-18 Thread masb...@za-management.com [firebird-support]
And another thing. Deactivating the triggers is not an option for me but it works. execute statement 'alter trigger files_au0 inactive'; execute statement 'alter trigger files_bu0 inactive'; execute statement 'alter trigger pool_loss_record_bu0 inactive'; update fil

[firebird-support] Re: Cross database update

2014-11-18 Thread masb...@za-management.com [firebird-support]
Hi Sean I think not. When you look at it, the two tables could also be located in one db ad then the for select update loop should point to the same topic/question. How can I do this without using a block in the update part which sets the transaction property correctly but runs isolated apart fr

RE: [firebird-support] Re: Cross database update

2014-11-18 Thread 'Leyne, Sean' s...@broadviewsoftware.com [firebird-support]
Again, this question should be directed to the appropriate IBExpert support forum/list/group. Sean From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] Sent: November-18-14 12:00 PM To: firebird-support@yahoogroups.com Subject: [firebird-support] Re: Cross database

[firebird-support] Re: Cross database update

2014-11-18 Thread masb...@za-management.com [firebird-support]
HI! I have had feedback from IBExpert in respect of my block statement. The correct syntax is easy and looks like the following below. I can see in my trigger log that the update uses just one transaction but unfortunately the triggers fire although the preceding rdb$set for each record (as th