Status of MySQL support

O

OhSeeGee

New Member
Jan 15, 2022
24
1
3
Wishing I was in Jamaica
This topic was last actively discussed back in 2023 so I thought I would check in on this topic. I would like to deploy FS with a GUI for some customers, but there is always customer resistance to yet another DBMS in their environment. Since they already have MySQL expertise this is regularly a requirement in selection.

I read about pgsql being moved from the core to its own module (mod_pgsql) - but not sure what that means in terms of MySQL support. Any official work on the status of MySQL support within FusionPBX?
 
Last edited:
I'm not sure about the official position on mysql support but I believe there are some functions that use postgres and have no mysql equivalent. Postgres is also easy to replicate to give you high availability.
 
I looks like DjangoPBX offers full MySQL support, so I'll give that a try instead.

For the purpose of a config generator, (and simple logging) there really shouldn't be a need for Postgres specific features in FusionPBX. Maybe some day the db module will be abstracted and then open to other DBMS'.
 
FusionPBX did support MySQL in the past. I can appreciate that your company may be entrenched in MySQL and, therefore, continuing to use it for that reason.

As far as FusionPBX goes. The problem is that it's a lot of work to support multiple databases.
  • It increases the support workload.
  • More learning and training are required
  • More work is needed to migrate from one database vendor to another
  • More work to learn and maintain redundant databases for each database vendor.
  • More developer workload to support multiple SQL Queries for each database vendor.
PostgreSQL is a great database
  • Better support for advanced SQL Queries than MySQL.
  • Not owned by a single company
  • Has a more generous license
  • PostgreSQL has more features
    • Support for vector data for AI.
    • Support for POSTGIS geospatial data
We might consider MySQL again at some point. This would depend on whether people are willing to support it or not. So far, there hasn't been much interest in helping to support such a project for MySQL.
 
Last edited:
We're actually not entrenched with any product, but we have to respect the wishes of our customers. MySQL/MariaDB has almost 50% market share of open source DBMS, compared to 17% PostgreSQL (see https://6sense.com/tech/relational-databases/postgresql-market-share)

In a nutshell FusionPBX is a config generator and servers up the dialplan...not OLTP. I agree PostgreSQL is a great database, but if you want broader adoption you can't tell the market they are wrong.

Not trying to start a holy war about the best DBMS, just pointing out that adoption of FusionPBX would be easier with a different (or flexible) DB backend. There really is no NEED for features specific to PostgreSQL, but I understand that you may prefer them and may have already written code which uses PostgreSQL specific feature.
 
OhSeeGee said:
We're actually not entrenched with any product, but we have to respect the wishes of our customers. MySQL/MariaDB has almost 50% market share of open source DBMS, compared to 17% PostgreSQL (see https://6sense.com/tech/relational-databases/postgresql-market-share)
Click to expand...
The numbers will depend on where you look.
As far as FusionPBX goes. The problem is that it's a lot of work to support multiple databases. I thought of a few more and since it didn't seem like you read my previous list here it is with a few additions.
  • Supporting multiple database vendors increases the support workload.
  • More learning and training are required
  • More work is needed to migrate from one database vendor to another
    • I migrated several people from MySQL to PostgreSQL.
  • More work to learn and maintain redundant databases for each database vendor.
  • More developer workload to support multiple SQL Queries for each database vendor.
    • PostgreSQL is far better at advanced SQL Queries
  • Testing new code will take longer when having to test multiple databases.
  • MySQL support will come with an expectation of supporting MariaDB.
Despite what I just said. I'll think about it some more and consider your request.
 
  • Like
Reactions: babak
You must log in or register to reply here.
Top Bottom