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-consu
Hi Lars,
Make a lot of sense, and would free time in your team to provide more value
(seems you are not lacking ideas). I would say go for it, with maybe
dedicated documentation about how to move (even if it's basically using the
import/export feature "as is", may be worth a couple of hours to writ
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 disc
Hello Lars
I hope you are well.
I fully agree with your assessment and the benefits are clear.
Best regards,
JM
> El 08/09/2017, a las 10:26, Lars Helge Øverland escribió:
>
> Hi all,
>
> I want to bring up the idea of solely support PostgreSQL for DHIS 2 for
> production use to get feedback f
Hi Lars,
I think like the DHIS2 is a system that needs to be deployed on a large
scale, the choice to keep postgresql is ideal. In its recent version
Postgresql becomes more flexible when there is a lot of data. It becomes
very close to Oracle. the possibility of using the Json and its highly
devel
Dear Timothy,
What version are you running? We experienced the same at one point but
because we keep upgrading to the latest build of 2.27, it was later no
more. I cant remember the exact build number.
But try upgrading to the latest build and see.
Regards
Prosper Behumbiize, MPH
DHIS2 Implemen
Agree. As a prelude we can put the export import through its paces. Would
be great to have a volunteer mysql Guinea pig user that we could document a
migration.
On 8 Sep 2017 9:27 am, "Lars Helge Øverland" wrote:
> Hi all,
>
> I want to bring up the idea of solely support PostgreSQL for DHIS 2 f
Hi Lars
Fully agreed. To concentrate one one DB platforms will not only saves time
and effort, also being efficiency to the system and can make more use of
advance functionality of the PostgreSQL & PostGIS.
You will have our full support.
Hannan
On Fri, Sep 8, 2017 at 2:26 PM, Lars Helge Øverla
Hey Carlos,
If you need to import the external data as tracked entity instances within
a program, it means that you need to transform your data to json payload by
specifying the tracked entity_id, the orgunit and for each data values
theirs corresponding attribute_id. Then you can upload the creat
9 matches
Mail list logo
