Closed (works as designed)
Project:
Configuration Management
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Aug 2013 at 21:44 UTC
Updated:
13 Aug 2015 at 11:34 UTC
Jump to comment: Most recent
Comments
Comment #1
ohthehugemanatee commentedThis error is exactly what it says: the table already exists in your database, when configuration is trying to create the field. You'd get the same error with Features or with module_enable in the same circumstances, so this is not a bug.
I usually run into this issue when I create a field, then import a DB dump to "start over". Importing a DB dump doesn't remove tables, it just overwrites the ones mentioned in the dump. You end up with the tables from the old field, even though that field doesn't exist anymore. The solution is to actually wipe your database before you import from a dump.