Hello,
The Language Reference seems to indicate differently. From the
REALSQLDatabase.AutoCommit entry:
Determines whether the database commits changes automatically, or
whether changes open an implicit transaction that you must
explicitly close by calling Commit or Rollback. The default is
False: Changes open implicit transactions that you must close
explicitly.
Since adding a "begin transaction" query worked for Tim, I'm guessing
the language in the reference is misleading or maybe that I'm just
misunderstanding.
I recently moved a project from the SQLite plugin to the built-in
REALSQLDatabase class, and I removed all of the "begin transaction"
lines thinking they were now unnecessary. I haven't noticed any kind
of speed hit, but I'll have to take a closer look now to make sure.
Thanks,
Navdeep Bains
Bains Software
On Jan 16, 2007, at 12:04 PM, Andre Kuiper wrote:
Hi Tim,
In your code I couldn't find a "begin transaction" , if this is
missing I believe that every sql-insert or update is executed as a
seperate transaction which slows down the db-engine enormously. If
you insert in the begin a db.SQLSelect("begin transaction") all
inserts are in one batch added to the database as soon it gets the
commit. That should make a big difference in the speed.
HTH,
Andre
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
