MySQL to PostgreSQL converter
github.com
MySQL to PostgreSQL converter
1–10 of 37 posts
Re: MySQL to PostgreSQL converter
#2Re: MySQL to PostgreSQL converter
#3No 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.
Re: MySQL to PostgreSQL converter
#4No 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.
Hard to believe mysql doesn't include that data in one of it's dump formats.
Re: MySQL to PostgreSQL converter
#5Earlier quoted context omitted.
Hard to believe mysql doesn't include that data in one of it's dump formats.
It is supported, just not in XML dump format.
Re: MySQL to PostgreSQL converter
#6Re: MySQL to PostgreSQL converter
#7Earlier quoted context omitted.
It is supported, just not in XML dump format.
Ah. That's a relief, I was a little worried. But that makes it strange that someone, knowing of this limitation, would choose to start with the xml dump format.
What's the point of having a dump format that you can't use to restore your database properly?
Does it have a health warning advising that it's not a proper dump?
Re: MySQL to PostgreSQL converter
#8Re: MySQL to PostgreSQL converter
#9does the job for me
Re: MySQL to PostgreSQL converter
#10Works very well for me.
I think the only limitation is related to spatial data. I'm not aware of anything else.