| From: | "Rob Richardson" <Rob(dot)Richardson(at)rad-con(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: When are updates from inside transactions visible? |
| Date: | 2008-10-21 14:54:56 |
| Message-ID: | 04A6DB42D2BA534FAC77B90562A6A03DAFA257@server.rad-con.local |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Answering my own question: The change is not visible until the commit,
which is what I was expecting and hoping. I added a couple of buttons
to a dialog box in an application that connected to our database. In
the handler for one button, I began a transaction and updated a value.
In the handler for the other, I committed the transaction. After
clicking the first button, the old value appeared in PGAdmin. After
clicking the second, the new value appeared.
RobR
-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Rob Richardson
Sent: Tuesday, October 21, 2008 9:58 AM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] When are updates from inside transactions visible?
Correction from my previous post. The first word in the title should
have been "when", not "where".
RobR
--
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org) To
make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl Nack | 2008-10-21 15:02:26 | Re: How best to implement a multi-table constraint? |
| Previous Message | Tom Lane | 2008-10-21 14:36:20 | Re: exposing more parse was: Re: tsearch2: setting weights on tsquery |