Hi,
Would you mind giving details why dumping/reloading JSON should not be used
in production (putting aside HA problems, for sure).
TIA
Le 05/06/2019 à 14:01, Devender Kumar a écrit :
> Hi,
> *It's very complicated with not much explanation in question.*
> Its depend on where you want to do this process Development or Production.
> If it is development then and not holding a very large amount of data.
> then its not very complicated
> dump JSON > change database engine > load JSON.
> If its production end then you might have to write some scripts to copy data
> from one database (MySQL) to dump Into another database (PostgreSQL) in
> between you can use transition state of JSON OR XML
>
> Thank you
>
>
> On Tue, Jun 4, 2019 at 2:46 PM Julien Enselme
> <
julien....@bureauxlocaux.com <mailto:
julien....@bureauxlocaux.com>>
> wrote:
>
> Hi,
>
> At my company we recently made a switch from MySQL to PG. We used
>
https://pgloader.io/ to load the data from MySQL to PG. It reliable and
> quite fast (we had about 2GO of data to migrate in multiple table). The
> tool will handle table creation and data migration. As @Kiran said, try
> first in a test env. It may take a while depending on the amount of code
> that relies on MySQL specific features. I hope this helps!
>
> Regard,
> Julien Enselme
> Développeur chez BureauxLocaux
>
>
> Le mar. 4 juin 2019 à 00:56, Kiran Capoor <
kiranc...@gmail.com
> <mailto:
kiranc...@gmail.com>> a écrit :
> <mailto:
django-users...@googlegroups.com>.
> <mailto:
django...@googlegroups.com>.
> <
https://groups.google.com/d/msgid/django-users/97a3c018-86ee-462a-a21a-6d2a7971adc1%40googlegroups.com?utm_medium=email&utm_source=footer>.
> <mailto:
django-users...@googlegroups.com>.
> <mailto:
django...@googlegroups.com>.
>
https://groups.google.com/d/msgid/django-users/CABUQWg_hm7U__cwKJvFvvvR3osuz-MtswCL1YLA74pGdEvp_PA%40mail.gmail.com
> <
https://groups.google.com/d/msgid/django-users/CABUQWg_hm7U__cwKJvFvvvR3osuz-MtswCL1YLA74pGdEvp_PA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> <mailto:
django-users...@googlegroups.com>.
> <mailto:
django...@googlegroups.com>.
>
https://groups.google.com/d/msgid/django-users/CAANvM2%3DHjGDSL3_rX6adnkp-8o%2Bj9trx9as0AMC5VGpMw25nZA%40mail.gmail.com
> <
https://groups.google.com/d/msgid/django-users/CAANvM2%3DHjGDSL3_rX6adnkp-8o%2Bj9trx9as0AMC5VGpMw25nZA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> <mailto:
django-users...@googlegroups.com>.
> <mailto:
django...@googlegroups.com>.
>
https://groups.google.com/d/msgid/django-users/CAL%3D_h26ttWeRZ5cv4dADrmLg4upJC65zdg4%3Dw1GFc8qZLUU5nw%40mail.gmail.com
> <
https://groups.google.com/d/msgid/django-users/CAL%3D_h26ttWeRZ5cv4dADrmLg4upJC65zdg4%3Dw1GFc8qZLUU5nw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> <mailto:
django-users...@googlegroups.com>.
> <mailto:
django...@googlegroups.com>.
>
https://groups.google.com/d/msgid/django-users/CALZ%3DbEKFvRFucvU-LeMCR4ejLska64zGKjq0m_hhoRYxJxyZHw%40mail.gmail.com
> <
https://groups.google.com/d/msgid/django-users/CALZ%3DbEKFvRFucvU-LeMCR4ejLska64zGKjq0m_hhoRYxJxyZHw%40mail.gmail.com?utm_medium=email&utm_source=footer>.