En Wed, 21 Oct 2009 22:24:49 -0300, David Sfiligoi
escribió:
On Wed, 21 Oct 2009 00:45:21 -0300, Gabriel Genellina wrote:
If you want to keep the cursor open, you must commit the (implicit)
current transaction, even if it only contains selects (a rollback would
work too).
Alternatively, low
On Wed, 21 Oct 2009 00:45:21 -0300, Gabriel Genellina wrote:
>
> If you want to keep the cursor open, you must commit the (implicit)
> current transaction, even if it only contains selects (a rollback would
> work too).
> Alternatively, lower the transaction isolation level below "repeatable
> rea
-- Forwarded message --
From: David Sfiligoi
To: python-list@python.org
Date: Tue, 20 Oct 2009 21:41:10 -0500
Subject: mysql select some sort of caching
Hi
I am normally an SQLlite person because it just works... but I decided to
keep inproving my skills set and do my new project
En Tue, 20 Oct 2009 23:41:10 -0300, David Sfiligoi
escribió:
whatever prior date I put in the table's last task date colum somehow
they are not seen by the SELECT query
sqlcur.execute("SELECT `url`d` from `url_snapshot` WHERE `url` = %s and
`lastsnapshotdate` < %s",(url,currentdate))
that que
On Tue, Oct 20, 2009 at 7:41 PM, David Sfiligoi wrote:
> So normally I would open a connection and instentiate a cursor for my
> queries once at a global level(like find out if the current date is >
> than the last task date). Then go in an infinite loop that wait for data
> to arrive in the queu
Hi
I am normally an SQLlite person because it just works... but I decided to
keep inproving my skills set and do my new project using a MySQL database
backend because of the architecture decision I made(horizontal scalable
system via message queues). The project is architected around a rabbitmq
