#3513: Null value in table node_change, column path
----------------------------+-----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone:
Component: general | Version: 0.9.6
Severity: normal | Keywords: timeline
----------------------------+-----------------------------------------------
We have a problem where the resync command for a particular project fails,
and generates this error in the trac log:
{{{
OperationalError: ERROR: null value in column path violates not-null
constraint
}}}
We manage several projects using trac, each in a separate subtree of the
repository. I was able to trace the origin of this to someone copying from
outside the subtree to inside the subtree for this project.
A trac project which encompasses the entire repository does not have any
problem here.
My workaround has been to delete the primary key on the table
'''node_change''', which allows me to remove the not-null constraint on
the column '''path'''. This is fine, so long as I do not try to inspect
the specific changeset, when a separate error occurs.
We are running the latest trac code (as of today), with a postgres
database backend.
--
Ticket URL: <http://trac.edgewall.org/ticket/3513>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
