Charles V. wrote:
If you are trying to tell us that your code "works" under MySQL but not
under SQLite I want to see the proof. Otherwise I don;t believe you.
regards
Steve
PS: What does "imbricated " mean?
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Hi,
>
Thank for replying.
>
>
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 MySQLdb won't be compatible with sqlite3 (even
if I am using standard SQL). In fact I don't really understand why the
iterator isn't in some way "encapsulat ed". Does anybody tried to implemented
this functionality ?
>
Thank for replying.
>
>Either use a second cursor OR ensure you fetch all the data from the
>first .execute() first:
>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 MySQLdb won't be compatible with sqlite3 (even
if I am using standard SQL). In fact I don't really understand why the
iterator isn't in some way "encapsulat ed". Does anybody tried to implemented
this functionality ?
under SQLite I want to see the proof. Otherwise I don;t believe you.
regards
Steve
PS: What does "imbricated " mean?
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/