Hi,
> Both may be standard compliant, but if you're depending on
> implementation details, you may still get different behaviour.
> I'm pretty sure that MySQLdb always fetches the entire resultset from
> the server. The sqlite3 module uses what would have been called
> "server-side cursors" in rea
Hi,
Thank for replying.
> Either use a second cursor OR ensure you fetch all the data from the
> first .execute() first:
Are these really the only solutions ? I was expecting the same behavior than
MySQLdb module, which is, as sqlite3, DB-API 2.0 compatible.
It means a program written for MySQ
Hi,
I hope this is not already known. But Google wasn't any help. So here begins a
script to explain my problem.
-
import sqlite3
conn = sqlite3.connect(':memory:')
c = conn.cursor()
c.execute('''create table stocks
(date text, trans text, symbol text,
qty real, price re
