Ticket #3513 (closed defect: duplicate)
Opened 6 years ago
Last modified 5 years ago
Null value in table node_change, column path
| Reported by: | tjb@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | version control | Version: | devel |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
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.
Attachments
Change History
comment:1 Changed 6 years ago by anonymous
- Version changed from 0.9.6 to devel
comment:2 Changed 5 years ago by cboos
- Component changed from general to version control
- Keywords timeline removed
- Resolution set to duplicate
- Status changed from new to closed
See #3778.