| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Garry Saddington <garry(at)schoolteachers(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Losing data |
| Date: | 2008-06-19 18:11:43 |
| Message-ID: | 1213899103.22738.61.camel@jd-laptop |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2008-06-19 at 19:12 +0100, Garry Saddington wrote:
> On Thursday 19 June 2008 18:52, Adrian Klaver wrote:
> > -------------- Original message ----------------------
> > From: Garry Saddington <garry(at)schoolteachers(dot)co(dot)uk>
> > Seems like a transaction with no commit. Basically along as the session is
> > active the data is there but once the session is closed the data does not
> > persist.
> >
> Makes sense but what is to blame?
If this is indeed the problem, it is likely a lack of an explicit commit
to your connect object within zope. In pysocpg2 unless you set your
isolation level to something different it automatically creates a new
transaction for your session so if you don't do conn.commit() everything
you do will be rolled back.
Joshua D. Drake
> Regards
> Garry
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Garry Saddington | 2008-06-19 18:12:01 | Re: Losing data |
| Previous Message | Adrian Klaver | 2008-06-19 18:11:15 | Re: Losing data |