monotone - Bugs: bug #19518, pick a single command for...
You are not allowed to post comments on this tracker with your current authentication level.
bug #19518: pick a single command for automatable db upgrades, and stick to it
Submitter: | Roland McGrath <roland> | ||
Submitted: | Thu 05 Apr 2007 09:04:18 AM UTC | ||
Category: | command line UI | Severity: | 3 - Normal |
Item Group: | feature request | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: | 0.34 |
Spam posted by anonymous | |
Mon 16 Apr 2007 09:27:38 PM UTC, comment #1: |
Thomas Keller <tommyd>![]() |
Thu 05 Apr 2007 09:04:18 AM UTC, original submission:
It is rough being a packager of monotone with scripts for running unattended "easy" server installations. The natural thing is to want the init.d script to do automatically any db upgrades that are necessary before starting the server after a software upgrade.
|
Roland McGrath <roland> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
The problem is that db migrate not always needs a db regenerate_rosters call (f.e. for the transition between 0.33 and 0.34), however if you do something like the following scriptwise
$ mtn db migrate && mtn db regenerate_caches
monotone happily regenerates the caches even if it is not needed. And regenerating the caches can be quite time consuming for bigger databases. On the other hand, regenerate_caches makes perfectly sense as stand-alone command if you have messed around with db kill_rev_locally and need to clean up things, so I wouldn't certainly vote for (re)moving that either or putting it into db migrate. So, what about the following:
a) let mtn db migrate set a flag somewhere that the caches have to be regenerated (if this isn't already done) after a scheme migration
b) make mtn db regenerate_caches default behaviour to do nothing if no such flag is present and only start something if the flag is set or some --force option is given (I know Nathaniel hates --force option, but I think it would be quite useful here...)
Opinions?