Seen this before with similar sql, but never found the cause (I think it's some weird sql patch tool issue). But, assuming the sql is correct (and that seems the case here), loading the sql via phpMyAdmin works perfectly in these cases. note that the DB prefix, if any, needs to be added to the table names manually then.ERROR: Can not insert configuration_key "", it already existsNote: 1 statements ignored. See "upgrade_exceptions" table for additional details.
Bookmarks