From: rakesh at rakeshv.org (Rakesh Vidyadharan) Date: Fri, 11 Nov 2005 16:12:11 -0600 Subject: [Pljava-dev] Question regarding triggers and data visibility In-Reply-To: References: <75F39425D1954A4380D5C9E1D630CDC903EA9133@C2A007.stratford.auto.cooperintra.ctb> Message-ID: <8AB3CE88-F6BB-4CC2-92EC-899A25DCADCB@rakeshv.org> On Nov 11, 2005, at 4:07 PM, Rakesh Vidyadharan wrote: > > On Nov 11, 2005, at 3:57 PM, Burtenshaw, John J. wrote: > >> Thanks for the quick reply Rakesh. It turns out I was not using >> transaction blocks (i.e. allowing ?autocommit?) so I just tried >> the insert statement in a Begin/commit block and it did not make a >> difference. Any other ideas as to what could cause this strange >> phenomena? > I believe the problem is caused by the fact that the message is > sent from a trigger. If I am not mistaken, the database > modification would not have been committed until the trigger > returns successfully, at which point the transaction would have > been committed. Does the trigger just send a message, or does it > wait for a response? Come to think of it, since the trigger already has access to the information in the record being inserted, there should be no reason for the remote object to fetch the new record from the database. You should be able to send a transfer object with the data to the remote object. I do not think you will save any network bandwidth using this technique, since you will be spending some anyway to fetch from the database. -------------- next part -------------- An HTML attachment was scrubbed... URL: