Re: Scheme conversion MySQL to PGSQL
От
Michelle Konzack
Тема
Re: Scheme conversion MySQL to PGSQL
Дата
Msg-id
f702baef3eb70d39d116ed711d9d3f54.squirrel@webmail.tamay-dogan.net
Ответ на
Re: Scheme conversion MySQL to PGSQL (Igal @ Lucee.org)
Список
Дерево обсуждения
Scheme conversion MySQL to PGSQL "Michelle Konzack" <linux4michelle@tamay-dogan.net>
Re: Scheme conversion MySQL to PGSQL Alban Hertroys <haramrae@gmail.com>
Re: Scheme conversion MySQL to PGSQL James Keener <jim@jimkeener.com>
Re: Scheme conversion MySQL to PGSQL Melvin Davidson <melvin6925@gmail.com>
Re: Scheme conversion MySQL to PGSQL "Michelle Konzack" <michelle.konzack@tamay-dogan.net>
Re: Scheme conversion MySQL to PGSQL Andreas Kretschmer <andreas@a-kretschmer.de>
Re: Scheme conversion MySQL to PGSQL "Igal @ Lucee.org" <igal@lucee.org>
Re: Scheme conversion MySQL to PGSQL "Michelle Konzack" <michelle.konzack@tamay-dogan.net>
Re: Scheme conversion MySQL to PGSQL "Igal @ Lucee.org" <igal@lucee.org>
Hello Igal Am 2017-12-24 hackte Igal @ Lucee.org in die Tasten: > 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? I convert only those four CREATE TABLE from mySQL to pgSQL which is the forum pluging for squirrelmail. auto_increment -> serial int(NN) -> int datetime -> timestamptz (attention: it is NOT timestamp) longtext -> text ENGINE=MyISAM hast to be removed. This are things, which I found on the internet. Greetings Michelle -- Michelle Konzack 00372-54541400
В списке pgsql-general по дате отправления