Jonas Schäfer authored Nov 28, 2017 and louiz’ committed Dec 02, 2017

(cf. https://www.postgresql.org/docs/9.4/static/libpq-connect.html#LIBPQ-CONNSTRING)

 close_v2(), in use before this commit, was introduced as part of sqlite 3.7.14
 (2012-09-03), and is as such incompatible with debian wheezy (3.7.13) and
 centos6 (3.6.20).
 FTR, Wheezy will be supported until May 2018, and centos6, until November 2020.

fix #3293

This immensely speeds up the archive select queries.

fix #3292

fix #3290

If we can’t open it at startup, we exit.
If we can’t open it on reload, we keep the previously-opened database.

This way, we’re assured to always have a valid and open database available.

Entirely replace LiteSQL

fix #3271

This makes us compatible with mam 6.0

fix #3249

Avoids a conflict between /usr/include/uuid.h and
/usr/local/include/uuid/uuid.h on freebsd

At the moment, result-set-management is not implemented, the whole history
(well, at most 1024 messages) is returned.

Instead of doing a broken SQL request that returns weird lines

Do not use a singleton for the database.

fix #3203

And a way to retrieve its values, defaulting on the ServerOptions for unset
values.

Uses litesql