Re: results via pgAdmin but not via psycopg2

From: Krystian Samp <samp(dot)krystian(at)gmail(dot)com>
To: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
Cc: psycopg(at)postgresql(dot)org
Subject: Re: results via pgAdmin but not via psycopg2
Date: 2013-12-31 13:14:30
Message-ID: 52571CFE-311F-4A57-8170-DCD2CBBFB259@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

Thanks,

This sounds good,

Would a commit() be considered slow or undesirable?

K

On 31 Dec 2013, at 13:09, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> wrote:

> On Tue, Dec 31, 2013 at 12:52:51PM +0000, Krystian Samp wrote:
>
>> Thank you so much, this was the problem indeed, and “connection.commit()” solved it.
>>
>> Didn’t think about committing after a SELECT command.
>
> If you want to spare the commit you may want to look at statement_timestamp();
>
> Karsten
> --
> GPG key ID E4071346 @ gpg-keyserver.de
> E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
>
>
> --
> Sent via psycopg mailing list (psycopg(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/psycopg

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Adrian Klaver 2013-12-31 15:31:33 Re: results via pgAdmin but not via psycopg2
Previous Message Karsten Hilbert 2013-12-31 13:09:58 Re: results via pgAdmin but not via psycopg2