Home ›
Sequences table fields must have same prefixes as tables themselves doSequences table fields must have same prefixes as tables themselves do
Submitted by Benjamin Melançon on July 19, 2007 - 11:33am
Agaric had an unexpected problem with sequences table after moving an existing site- it ignored what we had and started making new entries for menu_id and such ones with the database table as the prefix. The result was duplicate key errors on menu mid and new content being subsumed into the first posts and all-around utter weirdness.
So, here's the fix:
If you move a site from an environment without table prefixes, or if you are changing the prefix in addition to all the create table and insert statements you'll want to find and replace with the new prefix, you also want to go into the sequences table and prefix the fields in it.
As we were making the mselvesite single signon, also, we falsely suspected the innocent module. Actually, single sign-on wasn't even involved.
Agaric searched for in trying to solve this problem:
single sign on sequences prefixes drupal
sequences field prefixes Drupal
Agaric had an unexpected problem with sequences table after moving an existing site- it ignored what we had and started making new entries for menu_id and such ones with the database table as the prefix. The result was duplicate key errors on menu mid and new content being subsumed into the first posts and all-around utter weirdness.
So, here's the fix:
If you move a site from an environment without table prefixes, or if you are changing the prefix in addition to all the create table and insert statements you'll want to find and replace with the new prefix, you also want to go into the sequences table and prefix the fields in it.
As we were making the mselvesite single signon, also, we falsely suspected the innocent module. Actually, single sign-on wasn't even involved.
Agaric searched for in trying to solve this problem:
single sign on sequences prefixes drupal
sequences field prefixes Drupal
Comments
Post new comment