Phillip J. Eby wrote: """ Gadfly does support transactions. However, it keeps tables entirely in memory. This can make it blindingly fast for some read-only operations, but it is much slower when committing transactions if the database is large. It is not suited to large DB operations. """ At some level the last sentence is true because upon checkpoint entire gadfly tables are written out to the file system. However it can be mitigated by doing checkpoints less frequently than commits. By default every commit generates a checkpoint, but for better transaction performance you might want to have one checkpoint for every 1000 commits if the database is largish. See the gadfly documentation. -- Aaron Watters === There ain't no sanity clause