dhis2-devs team mailing list archive

[Antonia - Pro <antonia@xxxxxxxxxxx>]

Hi Lars and community,
Even though we use MySQL and other DBMS for other projects, I think it's
best for DHIS2 to use and explicitly specify in the documentation that the
only supported DBMS is PostgreSQL.
At the beginning of our project we lost a lot of time testing DHIS 2 with
MySQL, only to discover that some of the problems we had were related to
the use of MySQL, which then resolved, starting to use PostgreSQL.
In my opinion, it is better to support a single DBMS that is well tested
and has all the necessary features (GIS etc.).

Regards,

Antonia


*Eng. Antonia Bezenchek*
CIO - ICT Engineer
*InformaPRO S.r.l.* via Guido Guinizelli, 98/100, Roma 00152, Italy
tel. +39 06 5882352 / +39 06 5502218, fax +39  06 62207168
cell. +39 366 4049561, P.IVA IT08095781004
www.informapro.it - *Follow us on* LinkedIn
<https://www.linkedin.com/company/informapro>

2017-09-08 10:26 GMT+02:00 Lars Helge Øverland <lars@xxxxxxxxx>:

> Hi all,
>
> I want to bring up the idea of solely support PostgreSQL for DHIS 2 for
> production use to get feedback from the community.
>
> The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only. The
> main ones are:
>
> 1. Supporting and testing for more than one database platform is
> time-consuming. The majority of DHIS 2 implementations is using PostgreSQL
> already.
>
> 2. PostgreSQL supports advanced geospatial features through PostGIS. We
> are already depending on these for the GIS module to work optimally (i.e.
> for event clustering in GIS). There are no direct equivalent in e.g. MySQL.
> We are also considering using PostGIS data types in main data model.
>
> 3. PostgreSQL will provide some impressive features which will become very
> useful for us in version 10
> <https://wiki.postgresql.org/wiki/New_in_postgres_10> and 11. E.g. native
> partitioning, parallel queries, logical replication, foreign tables and
> improved query performance will be useful and allow us to develop the next
> DHIS 2 analytics solution.
>
>
> We are aware this will be inconvenient for users of other databases such
> as MySQL, but there is the option of migrating your database through the
> DHIS 2 metadata and data value import-export feature.
>
> On a technical note, we will keep the Hibernate development framework and
> keep supporting the H2 database for unit testing purposes.
>
> Please let us know your thoughts on this.
>
> regards,
>
> Lars
>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> lars@xxxxxxxxx
> http://www.dhis2.org <https://www.dhis2.org/>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>