| From: | Vincent Veyron <vincent(dot)veyron(at)libremen(dot)org> |
|---|---|
| To: | Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Alban Hertroys <haramrae(at)gmail(dot)com>, David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Re: any way for a transaction to "see" inserts done earlier in the transaction? |
| Date: | 2014-04-17 17:33:45 |
| Message-ID: | 20140417193345.59694cd13f24d265d5f7b174@libremen.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 17 Apr 2014 10:02:00 -0700
Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> wrote:
> I moved the code in the function inline into the code, and I still cannot
> find the newly inserted id the next time through the loop.
I suppose you use DBD::Pg, whose current default isolation transaction level is ``Serializable''
Don't know if it applies, but the Postgresql's documentation says this :
SERIALIZABLE
All statements of the current transaction can only see rows committed before the first query or data-modification statement was executed in this transaction. If a pattern of reads and writes among concurrent serializable transactions would create a situation which could not have occurred for any serial (one-at-a-time) execution of those transactions, one of them will be rolled back with a serialization_failure SQLSTATE.
--
Regards, Vincent Veyron
http://libremen.com/
Legal case, contract and insurance claim management software
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2014-04-17 17:34:50 | Re: Arduino SQL Connector |
| Previous Message | Susan Cassidy | 2014-04-17 17:02:00 | Re: Re: any way for a transaction to "see" inserts done earlier in the transaction? |