MySQL to PostgreSQL converter • Hacker News Board

Re: MySQL to PostgreSQL converter

#21

Post by olefoo » Sat, Feb 28, 2015, 5:49 PM UTC

sarciszewski wrote: post #13

pgib wrote: post #12

When I saw this was a PHP project: https://dl.dropboxusercontent.com/u/31250/gifs/no-thanks.gif

Really? What does the language it's written in have to do with anything at all here?

Just because a few very disciplined people can make something clean and functional in a language does not mean it's a strength of the language. PHP is great as a template language, but when it comes to manipulating data it's somewhat louche approach to data types is a liability.

Re: MySQL to PostgreSQL converter

#22

Post by scrollaway » Sat, Feb 28, 2015, 6:03 PM UTC

jeltz wrote: post #8

I would recommend using pgloader ( http://pgloader.io/ ) instead. It is simple to use in the default case, but can be configured with rules for how data types should be converted if necessary. It can also clean up weird timestamps like 0000-00-00 00:00:00.

Seconded. Used pgloader to turn a massive mysql database into postgres. Turned out great.

Re: MySQL to PostgreSQL converter

#23

Post by adamferguson » Sat, Feb 28, 2015, 6:07 PM UTC

jeltz wrote: post #8

I would recommend using pgloader ( http://pgloader.io/ ) instead. It is simple to use in the default case, but can be configured with rules for how data types should be converted if necessary. It can also clean up weird timestamps like 0000-00-00 00:00:00.

Upvote for pgloader. Moving data from SQL Server into Postgres with PGLoader has been fairly seamless and the maintainer is very responsive on Github.

Re: MySQL to PostgreSQL converter

#24

Post by mihailshumilov » Sat, Feb 28, 2015, 7:29 PM UTC

Thanks for Your comments It's really very important for me I think that next version of converter will be supported raw dump format

Re: MySQL to PostgreSQL converter

#25

Post by codexon » Sat, Feb 28, 2015, 8:01 PM UTC

I find the more difficult issue to be rewriting bulk "insert ignore" and "on duplicate key" queries.

Re: MySQL to PostgreSQL converter

#26

Post by tiglionabbit » Sat, Feb 28, 2015, 8:21 PM UTC

codexon wrote: post #25

I find the more difficult issue to be rewriting bulk "insert ignore" and "on duplicate key" queries.

Yeah, seems like postgres is the only database that doesn't support those things. I mean, I use postgres, but I curse the lack of this feature regularly.

Re: MySQL to PostgreSQL converter

#27

Post by maligree » Sat, Feb 28, 2015, 9:09 PM UTC

bjacobel wrote: post #2

No foreign key support is kind of a deal-breaker. Hard to believe anyone who is actually in the position of needing this would have a schema so simple that it contains no foreign keys.

> so simple

or complex

Re: MySQL to PostgreSQL converter

#28

Post by jaytaylor » Sat, Feb 28, 2015, 9:39 PM UTC

tiglionabbit wrote: post #26

codexon wrote: post #25

I find the more difficult issue to be rewriting bulk "insert ignore" and "on duplicate key" queries.

Yeah, seems like postgres is the only database that doesn't support those things. I mean, I use postgres, but I curse the lack of this feature regularly.

Which other databases support "insert ignore"?

Re: MySQL to PostgreSQL converter

#29

Post by anacleto » Sat, Feb 28, 2015, 9:39 PM UTC

jeltz wrote: post #8

I would recommend using pgloader ( http://pgloader.io/ ) instead. It is simple to use in the default case, but can be configured with rules for how data types should be converted if necessary. It can also clean up weird timestamps like 0000-00-00 00:00:00.

+1 pgloader.

Re: MySQL to PostgreSQL converter

#30

Post by louthy » Sat, Feb 28, 2015, 9:59 PM UTC

adamferguson wrote: post #23

jeltz wrote: post #8

I would recommend using pgloader ( http://pgloader.io/ ) instead. It is simple to use in the default case, but can be configured with rules for how data types should be converted if necessary. It can also clean up weird timestamps like 0000-00-00 00:00:00.

Upvote for pgloader. Moving data from SQL Server into Postgres with PGLoader has been fairly seamless and the maintainer is very responsive on Github.

There doesn't seem to be any mention of SQL Server on the site? I am in the process of researching a move to Postgres from SQL Server, so if you have any other info on how you achieved this that'd be very much appreciated.

EDIT I see it now. Still, anything that you think useful would be great :)