Re: results via pgAdmin but not via psycopg2
От | Krystian Samp |
---|---|
Тема | Re: results via pgAdmin but not via psycopg2 |
Дата | |
Msg-id | 52571CFE-311F-4A57-8170-DCD2CBBFB259@gmail.com обсуждение исходный текст |
Ответ на | Re: results via pgAdmin but not via psycopg2 (Karsten Hilbert <Karsten.Hilbert@gmx.net>) |
Ответы |
Re: results via pgAdmin but not via psycopg2
|
Список | psycopg |
Thanks, This sounds good, Would a commit() be considered slow or undesirable? K On 31 Dec 2013, at 13:09, Karsten Hilbert <Karsten.Hilbert@gmx.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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/psycopg
В списке psycopg по дате отправления: