Overview
Artifact ID: | 89aa282f19bb3f634b3ca821be35526cc0216586 |
---|---|
Ticket: | 43bf069f44586396669e7b3e2e75e5245950293c
rebuild hint after updating to a newer fossil version |
User & Date: | anonymous 2010-03-19 09:15:57 |
Changes
- comment changed to:
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.
- foundin changed to: "73c24ae363"
- severity changed to: "Minor"
- status changed to: "Open"
- title changed to:
rebuild hint after updating to a newer fossil version
- type changed to: "Feature_Request"