If I name my migration set MyMigrationSet, it will not be able to analyze the map and messages tables. The error after saving the content set is

Could not analyze migrate_map_MyMigrationSet

Schema also reports that the tables are not present, because the tables created are in lower case migrate_msgs_mymigrationset and migrate_map_mymitrationset.

Changing the set name to all lower case eliminated the error.

Comments

mikeryan’s picture

Version: 6.x-2.x-dev » 6.x-1.x-dev
mikeryan’s picture

Status: Active » Postponed (maintainer needs more info)

For me (on MySQL), the map and message tables get created in mixed case and there's no problem analyzing them. Are you using MySQL or Postgres? Any db parameters that might be forcing lowercase table names?

verta’s picture

Using MySQL 5.1.36, from WAMP, so this is on Windows. Looks like, Yes is the answer to the question that there is a db parameter, the default may be involved.

http://dev.mysql.com/doc/refman/5.5/en/identifier-case-sensitivity.html

"How table and database names are stored on disk and used in MySQL is affected by the lower_case_table_names system variable, ... On Windows the default value is 1. ...
1 Table names are stored in lowercase on disk and name comparisons are not case sensitive. MySQL converts all table names to lowercase on storage and lookup. This behavior also applies to database names and table aliases."

http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysv...

Changing this to "2" might be a workaround, so I'll try that. If it helps, perhaps this could be rephrased as a feature request to make the migration set names case insensitive.

mikeryan’s picture

Category: bug » task
Status: Postponed (maintainer needs more info) » Active

Yes, forcing lower-case (as Migrate 2 does) makes sense.

mikeryan’s picture

Status: Active » Fixed

Done - map and message table names are created and referenced as lowercase.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.