Ticket UUID: | 43bf069f44586396669e7b3e2e75e5245950293c | ||
Title: | rebuild hint after updating to a newer fossil version | ||
Status: | Open | Type: | Feature_Request |
Severity: | Minor | Priority: | |
Subsystem: | Resolution: | Open | |
Last Modified: | 2013-01-25 18:50:52 | ||
Version Found In: | 73c24ae363 | ||
Description & Comments: | |||
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. |