On Wed, Jun 20, 2012 at 7:04 PM, Niphlod <niph...@gmail.com> wrote: > You're forgetting another "layer". DAL leverages on DBAPI implementation of > sql drivers.
Well, that's not exactly good news for transparency and ease of documentation. > A little more complicated: get on an infinite loop inserting 10 rows, > without committing. while the loop is running on 1, try a loop of 100 > updates to those records, then commit. Occasionally you'll be presented with > "Database is locked" error. OK. But what I would prefer to do is actually reason about what should be happening rather than just slapping code together and trying to hope that my tests will be close enough to real world scenarios to be valid. Sure, there is documentation about the quirks of SQLite, but nothing (unless I've missed it after repeated reading) about the assumptions/defaults, etc of how the DAL uses the intermediate glue layers (pysqlite, etc.). At this point, I think I'll just avoid using the DAL unless it is part of the web2py application, it's easier to write the external server to talk directly to the relevant database. Thanks for your help! -=Doug --
