On Wed, 1 Sep 2004, Christian Smith wrote:
A transaction gives you a snapshot in time of the database. You may need to do more than one query, and require a consistent snapshot for the duration of the multiple queries.
this is definitely a real world need - in my latest code i have a 'snapshot' method that copies the database, runs PRAGMA integrity_check on it (perhaps repeating step one), and then uses a db handle on that db. tests have shown that this is consistently faster than aquiring any kind of read lock and running queries in the context of that lock - this probably has something to do with the fact that ALL my write operationns are bundled in transactions. in any case, builtin functionality for something akin to this would be fantastic.
-a
--
===============================================================================
| EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
| PHONE :: 303.497.6469
| A flower falls, even though we love it;
| and a weed grows, even though we do not love it. | --Dogen
===============================================================================
