We have a partner who would strongly prefer to use MySQL instead of Postgres as the DHIS 2.21 database. The DHIS documentation notes that MySQL can be used but doesn’t give much detail beyond the connection strings.
Does anyone in this group have experience with using MySQL for DHIS? Has it been reliable? Do you have to do any manual configuration that you wouldn’t do with Postgres?
in order to use MySQL there is nothing else you need to do (beyond changing the database connection config properties like you say).
Now MySQL is far less tested with DHIS 2 compared to Postgres so you are more likely to come across bugs and upgrade issues on MySQL.
There is also a fair chance that we will create Postgres-only features at some point in the future (as an example, using features from the PostGIS spatial data extension).
We have a partner who would strongly prefer to use MySQL instead of Postgres as the DHIS 2.21 database. The DHIS documentation notes that MySQL can be used but doesn’t give much detail beyond the connection strings.
Does anyone in this group have experience with using MySQL for DHIS? Has it been reliable? Do you have to do any manual configuration that you wouldn’t do with Postgres?
we tried to use MySQL, but it didn't work when we had to use
OptionsSet values in DataElements for single events without
registration. The OptionSet resulted empty, evidently because of some
problem fetching data from MySQL.
Iuri
···
2015-12-02 17:14 GMT+01:00 Lars Helge Øverland <larshelge@gmail.com>:
Hi Rebecca,
in order to use MySQL there is nothing else you need to do (beyond changing
the database connection config properties like you say).
Now MySQL is far less tested with DHIS 2 compared to Postgres so you are
more likely to come across bugs and upgrade issues on MySQL.
There is also a fair chance that we will create Postgres-only features at
some point in the future (as an example, using features from the PostGIS
spatial data extension).
So MySQL works, but Postgres would be preferred.
best regards,
Lars
On Wed, Dec 2, 2015 at 4:29 PM, Smith, Rebecca A. <rs3524@cumc.columbia.edu> > wrote:
Hi all,
We have a partner who would strongly prefer to use MySQL instead of
Postgres as the DHIS 2.21 database. The DHIS documentation notes that MySQL
can be used but doesn’t give much detail beyond the connection strings.
Does anyone in this group have experience with using MySQL for DHIS? Has
it been reliable? Do you have to do any manual configuration that you
wouldn’t do with Postgres?
-----Original Message-----
From: Iuri Fanti [mailto:iuri.fanti@gmail.com]
Sent: Wednesday, December 02, 2015 12:24 PM
To: Lars Helge Øverland
Cc: Smith, Rebecca A.; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] MySQL for DHIS
Hi,
we tried to use MySQL, but it didn't work when we had to use OptionsSet values in DataElements for single events without registration. The OptionSet resulted empty, evidently because of some problem fetching data from MySQL.
Iuri
2015-12-02 17:14 GMT+01:00 Lars Helge Øverland <larshelge@gmail.com>:
Hi Rebecca,
in order to use MySQL there is nothing else you need to do (beyond
changing the database connection config properties like you say).
Now MySQL is far less tested with DHIS 2 compared to Postgres so you
are more likely to come across bugs and upgrade issues on MySQL.
There is also a fair chance that we will create Postgres-only features
at some point in the future (as an example, using features from the
PostGIS spatial data extension).
So MySQL works, but Postgres would be preferred.
best regards,
Lars
On Wed, Dec 2, 2015 at 4:29 PM, Smith, Rebecca A. > <rs3524@cumc.columbia.edu> > wrote:
Hi all,
We have a partner who would strongly prefer to use MySQL instead of
Postgres as the DHIS 2.21 database. The DHIS documentation notes that
MySQL can be used but doesn’t give much detail beyond the connection strings.
Does anyone in this group have experience with using MySQL for DHIS?
Has it been reliable? Do you have to do any manual configuration that
you wouldn’t do with Postgres?
But I suggest to use Postgres other wise you get plenty of bugs. We use MySQL since 2011 and then we converted all our databases to postgres for various reasons.
we tried to use MySQL, but it didn’t work when we had to use OptionsSet values in DataElements for single events without registration. The OptionSet resulted empty, evidently because of some problem fetching data from MySQL.
Agree with the earlier responses, but we really should still try to stamp out the mysql bugs, since many organizations have large investments around that platform (and I think we are pretty close). However, users will have to do more tests themselves before upgrades.
we tried to use MySQL, but it didn’t work when we had to use OptionsSet values in DataElements for single events without registration. The OptionSet resulted empty, evidently because of some problem fetching data from MySQL.