Comment Re:and so meanwhile... (Score 1) 245
Some fair points, but...
* mysqldump | psql doesn't work even with --compatibe=postgresql: ints have precision (int(11)) and comments don't work the same
If MySQL has a --compatible=postgresql option that doesn't actually produce PostgreSQL-compatible output, then that's pretty unambiguously MySQL's fault, and not something that PostgreSQL can do a great deal about.
True, and I'm certainly not putting blame on Postgres, but it would be nice if they had a pg_mysql_import_from_dump as MySQL's compatibility is b0rked.
I see various scripts out there, on Github for example, that claim to aid in the transfer. But it seems the consensus that manual fiddling is required. Perhaps I should make a name for myself by building something that eases the process. A "pg_mysql_import_from_dump" as it were.
No way to "use dbname" for switching DBs inside psql - must quit and restart with different dbname
\connect, or alternatively, use schemas instead of databases and SET SEARCH_PATH.
Ah, good idea. Schemas are an option but if transferring a, say, Drupal install over, one doesn't want to have to ensure that the schema is prepended onto all SQL. I prefer to have individual DBs. So when in psql, I shall try \connect. And... it works perfectly. Thank you.
Issues with double quotes vs single quotes vs ticks - no opinion on which is best way to go but would be nice if a translation were available
MySQL being wildly non-standard.
Again, not disagreeing.