Hi all,
some thoughts about sqla and sqlite3. is it an issue, that sqla throws
an operationalerror with the message "the database is locked" in case of
too many concurrent operations on one db file? i found a post about this
problem with trac some years ago...
i tested a script for loading stuff from a web service and save it into
a sqlite db with sqla...
i use 20 or more concurrent processes to load the data and fill the db...
every time this error occurs the operating process terminates, so i
catch this error, invoke a session.rollback() manually and recurse into
saving the object again, in order to continue the process...
why isn't the rollback implicit when this error occurs? i think it is
not possible to retry the commit, is it? if i remember correctly this
throws a new exception
--
Greetings
Jan Müller
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@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.
