https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092019-03-21T19:27:47ZOpen Source Mobile CommunicationsOsmoHLR - Feature #3830: make downward compatible db-schema updates automatichttps://projects.osmocom.org/issues/3830?journal_id=136172019-03-21T19:27:47Zroh
<ul></ul><p>it seems i did not explain verbosely enough what i mean in detail:</p>
<p>we now have a mechanism which checks db versioning and also one which allows for schema-upgrades (when using -U)</p>
<p>sadly we have no 'error reporting' into the rest of the system whatsoever, so existing setups stop working when updating packages and restarting the services.</p>
<p>the admin has only ONE chance to find out whats wrong, and that is noticing that one of many osmo-* daemons is not running anymore by accident.<br />also none of the other services have any output that the hlr is not runnning/accessible.</p>
<p>i do not know if it would make sense to add the latter (error/warn in e.g. msc if hlr is unreachable)</p>
<p>but since we have not had any incompatible db-schema-updates so far (please correct me if i am wrong here),<br />i am suggesting running backwards-compatible db-updates automatically (while keeping a copy of the old hlr.db as hlr.db_bak_dbverX or such).</p>
<p>i fully understand that doing fully automatic db upgrades seem scary, but silently breaking our users setups is inviting a world of pain in customer support.<br />also i do not see a reason for doing that we all we did so far is <em>ADD</em> some colums to the db, which for sure not break any select statements of older versions.</p>
<p>if we really do INcompatible updates in the future, i propose bumping the db-versioning in a major/minor scheme and also explicitly warn users in the changelog/releasenotes.</p> OsmoHLR - Feature #3830: make downward compatible db-schema updates automatichttps://projects.osmocom.org/issues/3830?journal_id=153272019-07-18T06:15:31Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> OsmoHLR - Feature #3830: make downward compatible db-schema updates automatichttps://projects.osmocom.org/issues/3830?journal_id=220212021-04-28T08:45:34Zosmith
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>We discussed this topic again and arrived at a new solution: <a class="issue tracker-2 status-3 priority-2 priority-default closed" title="Feature: Automatically upgrade the database in a post-install script and create a backup (Resolved)" href="https://projects.osmocom.org/issues/5138">#5138</a></p>
<p>Closing this one.</p>