coldpizza wrote:
> Thanks a lot, Roel, adding a single commit() at the end did solve the
> speed problem.
>
> Another question is do I have to explicitly close the DB connection,
> or is it automatically garbage collected? Is it Ok to no have any
> cleanup code?
>
> Another question would be how
Steve Holden <[EMAIL PROTECTED]> writes:
> # We try to ensure the database is always closed by registering
> # the nodule's close() function to be called on program exit
Ooh! Where do I find more about writing Python nodules? Is it related
to cluster programming?
--
\"If you go parachu
coldpizza wrote:
> Thanks a lot, Roel, adding a single commit() at the end did solve the
> speed problem.
>
> Another question is do I have to explicitly close the DB connection,
> or is it automatically garbage collected? Is it Ok to no have any
> cleanup code?
>
It's generally OK, but you can r
Thanks a lot, Roel, adding a single commit() at the end did solve the
speed problem.
Another question is do I have to explicitly close the DB connection,
or is it automatically garbage collected? Is it Ok to no have any
cleanup code?
Another question would be how to define the encoding for newly
coldpizza schreef:
> I am trying to fill a sqlite3 database with records, and to this end I
> have written a class that creates the db, the table and adds rows to
> the table.
>
> The problem is that the updating process is *extremely* slow, and
> occasionally I get the message "database locked".
I am trying to fill a sqlite3 database with records, and to this end I
have written a class that creates the db, the table and adds rows to
the table.
The problem is that the updating process is *extremely* slow, and
occasionally I get the message "database locked".
I tried removing "self.con.com
