Hi Kern,

Kern Sibbald <k...@sibbald.com> writes:

> It has been a long time since the Bacula Community version supports
> SQLite3.  The code is still there, but it simply does not perform
> well, and so it is not at all suitable for a Bacula production
> environment.  The only two officially supported databases are MySQL
> and PostgreSQL, and providing that MariaDB remains reasonably
> compatible with MySQL, it will also work.

> It does not make any sense to hold up a Bacula release because of some
> problem with SQLite3.   If you do decide to hold up the release,
> please let me know so that I can completely remove the code in 9.0.4.

I would greatly prefer to be able to give users of Debian and it's
derivatives a warning before sqlite3 support is removed, especially
because sqlite/sqlite3 had been the default database in Debian
installations since the first Debian release that included Bacula
(Debian 3.1 in 2005). My predecessors in Bacula package maintenance
never changed that default. While I might be able to warn Debian users
by updating the current Bacula version in Debian stable to include such
a warning, that would not reach users of Debian derivatives (like
Ubuntu).

Anyway, attached to the bug reports (2305 + 2306) are now the patches
that I intend to use for the Debian packages.

 - Carsten

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to