Thanks, but unfortunately using the NullPool does not change the behavior. I guess I'll have to use another database system... sigh.
Thanks, -Samuel On 19 Jul., 16:33, Michael Bayer <mike...@zzzcomputing.com> wrote: > On Jul 19, 2010, at 10:16 AM, Samuel wrote: > > > Hi, > > > I am trying to access (write to) an SQLite database from multiple > > threads (no ORM), resulting in the following error: > > > "OperationalError: (OperationalError) database is locked" > > > The engine is created using the default SingletonThreadPool. Is there > > a way to do "graceful" locking to avoid this error? > > > (I am using sqlalchemy 0.4.8.) > > you'll probably have better luck using the NullPool with a file-based SQLite > database, but sqlite still allows only one writer at a time to access the > database. > > > > > > > -Samuel > > > -- > > You received this message because you are subscribed to the Google Groups > > "sqlalchemy" group. > > To post to this group, send email to sqlalch...@googlegroups.com. > > To unsubscribe from this group, send email to > > sqlalchemy+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/sqlalchemy?hl=en. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
