Closed (fixed)
Project:
Migrate
Version:
7.x-2.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Nov 2011 at 22:22 UTC
Updated:
12 Dec 2011 at 00:38 UTC
I have a migration from a database that is not default.
I've set it up, as recommended and for performance reasons, to put the "map" tables in the source database. I've done this by adding the source database name as the last argument to the MigrateSQLMap constructor. This seems to mean that the "message" tables also get created in the source database.
If I get any messages during a migration, clicking in the link fails saying the relevant table doesn't exist. It's looking in the default database for the messages.
Comments
Comment #1
mikeryanThat was easy enough - fix committed for D6 and D7, thanks!