[pkg-bacula-devel] Bug#854684: bacula doesn't officially support SQLite3
Sven Hartge
sven at svenhartge.de
Thu Feb 9 17:58:04 UTC 2017
Um 15:52 Uhr am 09.02.17 schrieb Carsten Leonhardt:
> Dear Serge,
>> Is it a good option to propose a default SQLite3 database ?
>>
>> SQLite3 is no longer supported :
>>
>> https://sourceforge.net/p/bacula/mailman/message/35656463/
>> https://sourceforge.net/p/bacula/mailman/message/35655925/
>>
>>> The code for SQLite3 remains in Bacula, but it is
>>> no longer supported. As far as I know, it works perfectly fine,
> thank you for your information. At the moment we are in freeze in
> preparation for the next Debian release, changes of this nature will no
> longer enter the next stable release. After the release, I will probably
> change the default to MariaDB/MySQL.
I was quite surprised to see sqlite3 being the default. I would have sworn
the default being MySQL.
But at least the description for bacula-director-sqlite3 mentions sqlitt3
being only useful for small or test installations. (Maybe we can put in a
warning via NEWS for Buster [too late for Stretch for that] that SQLite3
is unsupported and should no longer be used.)
Concerning the default database: I think upstream favors PostgreSQL.
Grüße,
Sven.
More information about the pkg-bacula-devel
mailing list