Harald Welte
d43c22ef65
The choice of libdbi was one of the biggest early mistakes in (back then) OpenBSC development. A database abstraction library that prevents you from using proper prepared statements. Let's finally abandon it and use sqlite3 directly, just like we do in osmo-hlr. I decided to remove the database migration code as it would be relatively cumbersome to port all of it to direct sqlite3 with prepared statements, and it is prone to introduction of all kinds of errors. Since we don't have a body of older database files and comprehensive migration tests, it is safer to not offer migration code of uncertain quality. The last schema revision (5) was introduced 5 years ago in 2017 (osmo-msc v1.1.0), so it is considered an exceptionally rare case. People can install osmo-msc 1.1.0 through 1.8.0 to upgrade to v5 before using this new 'direct sqlite3' version of osmo-msc. Change-Id: Ia334904289f92d014e7bd16b02b3b5817c12c790 Related: OS#5559, OS#5563, OS#5564 |
||
|---|---|---|
| .. | ||
| db_sms | ||
| mncc | ||
| msc_vlr | ||
| sdp_msg | ||
| smpp | ||
| sms_queue | ||
| Makefile.am | ||
| atlocal.in | ||
| ctrl_test_runner.py | ||
| smpp_test_runner.py | ||
| stubs.c | ||
| test_neighbor_ident.vty | ||
| test_nodes.vty | ||
| testsuite.at | ||
| vty_test_runner.py | ||