osmo-msc/src
Vadim Yanitskiy 570b4c8be2 libmsc/db.c: get rid of hard-coded SMS expiry threshold
The initial idea of the SMS expiry threshold was to avoid storing
SMS messages with too long validity time (e.g. 63 weeks).
Unfortunately, neither this feature was properly documented, nor
the expiry threshold is configurable. Moreover, it has been
implemented in a wrong way, so instead of deleting the oldest
expired message, it would delete the youngest one or nothing:

  SELECT ... FROM SMS ORDER BY created LIMIT 1;

while it should be sorted by 'valid_until' in ascending order:

  SELECT .. FROM SMS ORDER BY valid_until LIMIT 1;

Thus, if the oldest message is expired, it gets deleted. If the
oldest message is not expired yet, there is nothing to delete.

Change-Id: I0ce6b1ab50986dc69a2be4ea62b6a24c7f3f8f0a
2019-06-07 08:05:24 +07:00
..
libmsc libmsc/db.c: get rid of hard-coded SMS expiry threshold 2019-06-07 08:05:24 +07:00
libvlr sgs_iface: detect and react to VLR/HLR failure 2019-05-27 11:49:50 +00:00
osmo-msc build osmo-msc: add "missing" LIBASN1C_LIBS 2019-05-19 07:25:04 +00:00
utils configure.ac: drop useless SQLite3 dependency 2019-04-25 21:23:35 +02:00
Makefile.am Remove local libgsupclient; Use libosmo-gsup-client from osmo-hlr 2018-08-05 11:20:21 +02:00