Fossil SCM
rptsql and rptedit show wrong (incomplete) ticket schema
958876ce82d3b82…
· opened 12 years, 11 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Important
- Resolution
- —
- Subsystem
- —
- Created
- April 11, 2013 10:27 p.m.
The fossil web pages rptsql and rptedit to show and edit the sql of a ticket report show the ticket schema the user works with.
Unfortunately the schema shown is neither the default schema found in tktsetup.c/schema.c, nor the custom schema a user may have configured (entry "ticket-table" in table "config"). Well, actually it shows part of the latter, but not all.
At fault is the function report_format_hints() in report.c which pulls the schema for TICKET to show directly out of the fossil db. Which is nice and good, and completely forgets the table TICKETCHNG which may also exist. See the defaults referenced.
Comments (1)
The fossil web pages rptsql and rptedit to show and edit the sql of a ticket report show the ticket schema the user works with.
Unfortunately the schema shown is neither the default schema found in tktsetup.c/schema.c, nor the custom schema a user may have configured (entry "ticket-table" in table "config"). Well, actually it shows part of the latter, but not all.
At fault is the function report_format_hints() in report.c which pulls the schema for TICKET to show directly out of the fossil db. Which is nice and good, and completely forgets the table TICKETCHNG which may also exist. See the defaults referenced.