FAQ/When do I update stateVersion: Difference between revisions
→What even is system.stateVersion for, if it is just an unchanging string?: Make more explicit that people shouldn't be changing this setting, because somehow even a page full of FAQs saying you shouldn't doesn't get the point across. Tags: Mobile edit Mobile web edit |
→What even is system.stateVersion for, if it is just an unchanging string?: Clarify the perceived intent of `system.stateVersion` Tags: Mobile edit Mobile web edit |
||
| Line 29: | Line 29: | ||
== What even is <code>system.stateVersion</code> for, if it is just an unchanging string? == | == What even is <code>system.stateVersion</code> for, if it is just an unchanging string? == | ||
Currently, this is undefined<ref name=":1" />. | Currently, this is undefined<ref name=":1" />, though the intent is to keep track of on-disk state versions that are not supposed to change with the configuration. | ||
As a result, modules can effectively use | As a result, modules can effectively use <code>system.stateVersion</code> for anything, which makes the effects of changing it unpredictable. | ||
Since it is sometimes used to protect data integrity upon package updates, changing the number can lead to irreversible data loss. | Since it is sometimes used to protect data integrity upon package updates, changing the number can lead to irreversible data loss. | ||