pg.ddx.io  pljava-dev@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Subject: [Pljava-dev] Question regarding triggers and data visibility
Date: Fri, 11 Nov 2005 16:07:28 -0600
Message-ID: <FE106E7B-912A-4846-9993-0953F3786954@rakeshv.org> (raw)
In-Reply-To: <75F39425D1954A4380D5C9E1D630CDC903EA9133@C2A007.stratford.auto.cooperintra.ctb>
References: <75F39425D1954A4380D5C9E1D630CDC903EA9133@C2A007.stratford.auto.cooperintra.ctb>


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?

Rakesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20051111/774977a7/attachment.html;



view thread (7+ messages)  latest in thread

Message-ID: <FE106E7B-912A-4846-9993-0953F3786954@rakeshv.org>
Permalink:  ../FE106E7B-912A-4846-9993-0953F3786954@rakeshv.org/
Also on:    postgresql.org/message-id/FE106E7B-912A-4846-9993-0953F3786954@rakeshv.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pljava-dev@postgresql.org
  Subject: Re: [Pljava-dev] Question regarding triggers and data visibility
  In-Reply-To: <FE106E7B-912A-4846-9993-0953F3786954@rakeshv.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox