Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.After updating to .7 (and then the latest dev version), the tables renamed as the update indicated. However whenever i save a piece of content that was using the serial field i get an unexpected web site error because the serial table that the insert is attempted on does not exist.
From the logs:
INSERT INTO {serial_b636c4fb8cc1eea34bfb084214d610d4}
From the DB:
http://puu.sh/oFVDH/328d90293b.png
As you can see the update did not rename any of serial tables to what it's attempting to use. I have not deleted or changed anything on the site after the update. Any thing i can try without rolling back or loosing my current serial data?
Comments
Comment #2
robit8deb CreditAttribution: robit8deb commentedComment #3
robit8deb CreditAttribution: robit8deb commentedComment #4
robit8deb CreditAttribution: robit8deb commentedIf this happened to anyone else - the quick bandaid was to figure out which serial table you need updated and rename the table to whatever the code was trying to use. All four of my serial fields did not match what the code was trying to insert to.
Comment #5
MustangGB CreditAttribution: MustangGB commentedDid you update to 1.6 first then go to 1.7?
If so that is the problem, the 1.6 release broke the table names which was resolved in 1.7.
Comment #6
Michael-IDA CreditAttribution: Michael-IDA as a volunteer commented> If so that is the problem, the 1.6 release broke the table names which was resolved in 1.7.
'eh, no, 1.7 doesn't resolve the table names . . . At this point in time you're better reverting to 1.5 and waiting till this settles out.
See also: #2733589: Updating from 7.x-1.5 to 7.x-1.7 results in incorrect tables used.
Comment #7
Michael-IDA CreditAttribution: Michael-IDA as a volunteer commented