[Pljava-dev] Question regarding triggers and data visibility

Rakesh: You are right that I should be able to pass the new information to the Daemon through the network but the one inconvenient problem is that the ResultSet object is not serializable which is a requirement for RMI objects. I suppose I could break the result down to a serialized string stream or something to that effect. Can you think of another way?

Thanks again
John Burtenshaw

-----Original Message-----
From: pljava-dev-bounces at gborg.postgresql.org on behalf of Rakesh Vidyadharan
Sent: Fri 11/11/2005 5:12 PM
Cc: Pljava-dev at gborg.postgresql.org
Subject: Re: [Pljava-dev] Question regarding triggers and data visibility

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: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20051114/2798e85a/attachment.html>