#3444: Strange `database is locked` error: commit fails but data is nevertheless
saved...
---------------------+------------------------------------------------------
Reporter: cboos | Owner: jonas
Type: defect | Status: new
Priority: low | Milestone:
Component: general | Version: 0.9.6
Severity: normal | Keywords: database lock pysqlite
---------------------+------------------------------------------------------
I just tried to close #3410, and I got the following error message:
{{{
Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 314, in
dispatch_request
dispatcher.dispatch(req)
File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 199, in
dispatch
resp = chosen_handler.process_request(req)
File "/usr/lib/python2.3/site-packages/trac/ticket/web_ui.py", line 260,
in process_request
self._do_save(req, db, ticket)
File "/usr/lib/python2.3/site-packages/trac/ticket/web_ui.py", line 530,
in _do_save
db.commit()
OperationalError: database is locked
}}}
So far so good (well...) but when looking at the timeline immediately
after that, the change appears to have succeeded!
And that's really puzzling: if the commit fails, the data shouldn't
persist.
This is not the first time I see somthing like this, so now I've decided
to create a ticket about it. No milestone set, it's just a place to record
the issue and discuss it until what happens is understood...
--
Ticket URL: <http://trac.edgewall.org/ticket/3444>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
