Related to my earlier post, I'm seeing "no such table" errors when I try to run the migrator check. What I've noticed is that the queries that are failing all seem to have a dot (period) in the name of the table it's trying to access. And I did not include a dot in the prefix.

For example, the prefix I've defined in settings.php is 'ps_' and the error messages look like this:

General error: 1 no such table: ps_.block: SELECT b.* FROM {block} b WHERE (b.theme = :

and so on. I'm wondering why it's looking for ps_.block rather than ps_block which is what I would have thought that {block} would expand to.

Either there is a typo somewhere with an extra period character where it does not belong, or else I'm simply showing off my ignorance

Comments

josh waihi’s picture

josh waihi commented
Status: Active » Postponed (maintainer needs more info)

I just tried a MySQL -> PostgreSQL migration with a prefix on the PostgreSQL connection and that seemed to work fine on 7.x-1.4. So I might suggest upgrading the module.

Since it works from MySQL -> PostgreSQL, that means DBTNG Migrator is working, otherwise all databases would have a prefix issue. So I'd look to the SQLite driver as it may not support prefixes the way you'd like. Prefixes are poor mens schemas anyway as MySQL doesn't support SQL schemas, Drupal implemented prefixes to namespace its tables. However, if your migrating to SQLite, why do you even need to use prefixes?