https://osmocom.org/https://osmocom.org/favicon.ico?16647414092016-04-28T19:11:18ZOpen Source Mobile CommunicationsOpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=12742016-04-28T19:11:18Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=12802016-04-28T19:11:50Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-high2 closed" href="/issues/1592">Feature #1592</a>: VLR in libmsc, to connect to HLR asynchronously</i> added</li></ul> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=13892016-05-09T19:38:21Zlaforge
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li></ul> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=24372016-11-11T08:38:22Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>neels</i></li></ul> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=25342016-12-02T17:18:56Zlaforge
<ul><li><strong>Target version</strong> set to <i>Asynchronous HLR+AUC for CS</i></li></ul> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=25842016-12-09T00:42:07Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>I take it that once libvlr is in place, there will be no sqlite3 in osmo-nitb/osmo-cscn.<br />-> watch <a class="issue tracker-2 status-5 priority-4 priority-high2 closed" title="Feature: VLR in libmsc, to connect to HLR asynchronously (Closed)" href="https://osmocom.org/issues/1592">#1592</a></p> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=27282017-01-05T14:01:45Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-1 priority-lowest closed" href="/issues/1591">Bug #1591</a>: libdbi is buggy and slow, get rid of it</i> added</li></ul> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=27302017-01-05T14:04:52Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>neels wrote:</p>
<blockquote>
<p>I take it that once libvlr is in place, there will be no sqlite3 in osmo-nitb/osmo-cscn.</p>
</blockquote>
<p>Correction: there will be no integrated HLR in a directly used sqlite3 db. We will still<br />keep the SMS in an sqlite3 db, but synchronous access for SMS is not a problem.</p>
<p>With <a class="issue tracker-2 status-5 priority-4 priority-high2 closed" title="Feature: VLR in libmsc, to connect to HLR asynchronously (Closed)" href="https://osmocom.org/issues/1592">#1592</a> resolved, we should still verify beyond doubt that the sms queue will not block<br />on e.g. a locked sqlite3 db.</p> OpenBSC - Bug #30: sqlite3 database / asynchronous access to ithttps://osmocom.org/issues/30?journal_id=29232017-01-24T11:57:10Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>duplicate</i></li></ul><p>With the libvlr / OsmoHLR effort tracked in <a class="issue tracker-2 status-5 priority-4 priority-high2 closed" title="Feature: VLR in libmsc, to connect to HLR asynchronously (Closed)" href="https://osmocom.org/issues/1592">#1592</a>, keeping this ticket does not really make sense anymore.<br />When <a class="issue tracker-2 status-5 priority-4 priority-high2 closed" title="Feature: VLR in libmsc, to connect to HLR asynchronously (Closed)" href="https://osmocom.org/issues/1592">#1592</a> is done, access to the HLR data will be inherently asynchronous, via GSUP messaging.<br />(The SMS related issue shall be tracked in <a class="issue tracker-1 status-5 priority-1 priority-lowest closed" title="Bug: libdbi is buggy and slow, get rid of it (Closed)" href="https://osmocom.org/issues/1591">#1591</a> and is merely temporary anyway.)</p>