Hello Quentin, et al:
While I am thrilled to hear there is strong forward progress on SOGo6,
as a company we are */very/* distraught to hear that support for
MariaDB/MySQL is being dropped.
MariaDB support was one of the */key elements/* that caused us to
recently adopt SOGo -- as opposed to competing options which rely
exclusively on PostgreSQL.
PostgreSQL is a very impressive DBMS, but it is not necessarily a good
fit for all enterprises.
For one, this decision will now cause enterprises having standardized on
MariaDB/MySQL to ADD an element to their technology stack for a single
purpose. Adding another DBMS daemon to a host arguably "steals" compute
cycles and other resources from other daemons, adds cognitive and
perhaps other types of sysadmin and hardware "complexity" and a host of
possible other downsides.
Given that MariaDB recently seems to have virtually ALL the
functionality of PgSQL, could you speak a moment to /why/ this design
decision is being made? Especially with regard to */technical
requirements/*, for example? After all, working with MariaDB/MySQL on
Python seems just as trivial as it is with PostgreSQL. [ But feel free
to specifically dispute that if you believe I am wrong. ]
ALSO, is there currently any concept that adding "back" MariaDB
connectivity would be considered for version 6.x?
If not, I fear SOGo will lose quite a lot of adopters.
Thanks in advance for your more detailed insights into this decision.
Felix
On 9/29/25 08:30, qhivert ([email protected]) wrote:
Hello,
Yes there will be migration scripts from SOGo 5 MAriadb/Postgresql to SOGo 6
Postgresql.
-- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache
69002 Lyon www.alinto.com
