On 11/07/2011 05:04 PM, John Nagle wrote:
Realize that SQLite is not a high-performance multi-user database.
You use SQLite to store your browser preferences, not your customer
database.
I agree with SQLite is not multi-user; I disagree that SQLite is not a
high-performance database. In single
On 11/6/2011 12:04 PM, Dennis Lee Bieber wrote:
On Sun, 6 Nov 2011 11:39:56 +0200, "Frank Millman"
declaimed the following in gmane.comp.python.general:
So my analysis of the problem is correct, but my solution is wrong.
Instead of executing fetchall() and returning the connection, I should
r
Hi all
I am using a few DB_API adaptors - ceODBC for Sql Server, psycopg2 for
PostgreSQL, and sqlite3 for sqlite3.
They all offer the feature that if a cursor executes a SELECT, the cursor
returns an iterator which can be used to fetch one row at a time. I have
been using this feature for a
"Alain Ketterlin" wrote
"Frank Millman" writes:
I am using a few DB_API adaptors - ceODBC for Sql Server, psycopg2 for
PostgreSQL, and sqlite3 for sqlite3.
They all offer the feature that if a cursor executes a SELECT, the
cursor returns an iterator which can be used to fetch one row at a
t
"Frank Millman" writes:
> I am using a few DB_API adaptors - ceODBC for Sql Server, psycopg2 for
> PostgreSQL, and sqlite3 for sqlite3.
>
> They all offer the feature that if a cursor executes a SELECT, the
> cursor returns an iterator which can be used to fetch one row at a
> time. I have been u