Re: Scheme conversion MySQL to PGSQL
От | Igal @ Lucee.org |
---|---|
Тема | Re: Scheme conversion MySQL to PGSQL |
Дата | |
Msg-id | 1e666e62-f8f5-0a8d-db37-a98863aeb95d@lucee.org обсуждение исходный текст |
Ответ на | Re: Scheme conversion MySQL to PGSQL (Andreas Kretschmer <andreas@a-kretschmer.de>) |
Ответы |
Re: Scheme conversion MySQL to PGSQL
|
Список | pgsql-general |
On 12/24/2017 10:18 AM, Andreas Kretschmer wrote:
I agree with Andreas. First create the tables, then create the indexes. If you can copy the data before creating the indexes then you will probably save some time on all of the INSERTs.
I am doing a similar thing migrating from SQL Server, and I am considering to publish an open source Migrator.
Can you tell me about some of the data types that you had to change moving from MySQL to Postgres?
Thanks,
On 24 December 2017 18:52:39 CET, Michelle Konzack <linux4michelle@tamay-dogan.net> wrote:I try to convert a Database scheme from mySQL to pgSQL and have problems with the line: KEY post_date (post_date) and later probably with the lines UNIQUE KEY user (stat_login)That's just indexe. Create them later with create index ...
I agree with Andreas. First create the tables, then create the indexes. If you can copy the data before creating the indexes then you will probably save some time on all of the INSERTs.
I am doing a similar thing migrating from SQL Server, and I am considering to publish an open source Migrator.
Can you tell me about some of the data types that you had to change moving from MySQL to Postgres?
Thanks,
Igal Sapir
Lucee Core Developer
Lucee.org
В списке pgsql-general по дате отправления: