Fossil SCM
rebuild hint after updating to a newer fossil version
43bf069f4458639…
· opened 16 years ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Minor
- Resolution
- Open
- Subsystem
- —
- Created
- March 19, 2010 9:15 a.m.
i dont know if its a lack of documentation or if its just me, but i am confused about when to do a rebuild.
ok i know that if the table structure of fossil changes, i have to do a rebuild. but looking from the end-user perspective, i have no clue when an update changes the structure and when not.
i am still new to fossil, but as far as i know the user updates, try to executes a command and the command fails due to an old table structure and the user have to be so "clever" to rebuild before submitting a ticket...
what about saving inside the table structure the fossil version from the last rebuild and check for this version by every command. if i update now fossil, it recognizes that the structure is to old and gives a hint or just do a rebuild.
Comments (1)
To be perfectly reliable this would have to work at the UUID level, not version number level, and would mean that the fossil developers would be continually hounded by such a warning (which implies yet another config option to disable it).