#2902: OperationalError: SQL logic error or missing database
---------------------+------------------------------------------------------
Reporter: athomas | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone:
Component: general | Version: devel
Severity: major | Resolution:
Keywords: |
---------------------+------------------------------------------------------
Comment (by anonymous):
I came across this same error, which seems to be a generic (completely
useless IMO) catch-all error, when creating the unit tests for Trac Tags.
In that case, the unique constraint on a table was being violated because
multiple ticket changes were being inserted for the same timestamp.
Perhaps something similar is happening here with duplicate session
columns, or some other constraint violation.
Presumably if I switched to Postgres, I might get more useful errors that
might help track this down.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2902>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
