Re: [GENERAL] MySQL -> Postgres dump converter
От | Thomas Lockhart |
---|---|
Тема | Re: [GENERAL] MySQL -> Postgres dump converter |
Дата | |
Msg-id | 3A6DC891.8A767C1E@alumni.caltech.edu обсуждение исходный текст |
Ответ на | Re: [GENERAL] MySQL -> Postgres dump converter (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: [GENERAL] MySQL -> Postgres dump converter
Re: [GENERAL] MySQL -> Postgres dump converter |
Список | pgsql-hackers |
> Can some PostgreSQL people comment on this? This person wrote a > MySQL->PostgreSQL converter too. His version is at: > http://ziet.zhitomir.ua/~fonin/code -- THIS VERSION IS EXTREMELY BUGSOME ! USE IT ON YOUR OWN RISK !!! Hmm. My version does not have this feature, but it could be added ;) Seriously, I haven't looked at the differences, but there is a licensing difference (BSD vs GPL). Someone else with experience with MySQL should evaluate both packages. mysql2pgsql has been used to convert SourceForge, with ~90 tables and moderately complicated schema, but that did not include enumerated types (done with ints at SF) and "unique" keys (done with sequences at SF) afaicr. > Sucks found:... Each is a one-liner to fix in mysql2pgsql. The (nonstandard) types mentioned weren't used in the test cases I had available. I didn't realize that we had *any* reports of troubles or lacking features in the existing converter, but I'll leave it up to y'all to decide if the licensing issues and feature issues are significant. I'm willing to provide patches to address some of the concerns, but of course will not be able to look at the GPL'd code for hints and can only use the information posted here to help afaik. Comments? - Thomas
В списке pgsql-hackers по дате отправления: