Opened 19 years ago
Closed 18 years ago
#2943 closed defect (duplicate)
Timeline fails due to SQL errors
Reported by: | PBruin | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | devel |
Severity: | normal | Keywords: | sqlite3 |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Ticket changes, Ticket details event provider failed: OperationalError: cannot commit transaction - SQL statements in progress
When I tried loading the timeline I got this error. Some of the actions I did before this occured:
- I added new user using the register plugin
- Added his permissions using the admin module
- Added new wiki page
I manage to get the timeline to work again by loading it without ticket information and then adding it again. Before that I did restart apache but it did not solve the problem.
I have had this happen to me before and seem to recall that I also added some permissions around that time. I solved it the by dumping the database and reloading it.
Some system info:
Attachments (0)
Change History (6)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Keywords: | sqlite3 added |
---|
Which version of the PySqlite bindings for SQLite are you using?
comment:4 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think this is fixed in r3026.
After I updated to the last revision I did not see this problem anymore. But when I reverted to r3022 due to unicode related errors I got the error back (after some time). Restarting apache did not solve the problem. However updating to r3026 solved this problem for now.
Will close the ticket for now as I think it is solved.
comment:5 by , 18 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
I think that this was actually a duplicate of #2902.
comment:6 by , 18 years ago
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
It just happened again. I again managed to solve it by using this link on the page:
After that I added the ticket details and after that ticket changes.
Also to be sure I update my install to the latest version. Will keep you posted if it happens again.
Could it have something to do with a the post-commit hook that imports messages to tickets?