By coreyp_1 on

I post this so that it might be of use to someone who may also be having difficulties with their upgrade.

After upgrading my site, everything worked OK... most of the time. Every once in a while, I saw a php error about a duplicate ID or something in the watchdog or cache table, but it wasn't often enough to figure out the cause.

Then I noticed that when nodes were updated, their url alias disappeared, pathauto wansn't creating new aliases, and even paths that I explicitely typed into the node edit form weren't saved.

I was not able to add or edit Categories for the Contact module.

Other problems surfaced with different modules.

I finally figured out that, in my importing/exporting of databases, all of the auto_increment directived for table fields had been stripped! I don't know when or how I did it, but I did.

Long story short, I ended up going through each module's install schema (as well as the system install schema), and re-added the auto_increment command to the appropriate fields.

Thankfully my indexes were still there!

I hope this info will be of assistance to someone.

- Corey

⋅ Categories: Drupal 5.x

Comments

Igorific’s picture

Igorific commented

I get this same problem when I upload to my live server which runs MySQL 4.0.20

For example, when I execute this MySQL statement...

CREATE TABLE `access` (
  `aid` int(11) NOT NULL,
  `mask` varchar(255) NOT NULL default '',
  `type` varchar(255) NOT NULL default '',
  `status` tinyint(4) NOT NULL default '0',
  PRIMARY KEY  (`aid`)
) TYPE=InnoDB AUTO_INCREMENT=1 ;

The access table is, of course, created, but the "auto_increment" attribute for the "aid" field has been stripped.

So, like you, I have to go to each table individually, and put it back in. I realize this has nothing to do with Drupal, but what a hassle!!!

jonahan’s picture

jonahan commented

MAke sure to check the 'sequences' table. This holds ID's that Drupal thinks is the next ID - rather than what MySQL thinks should be the next one.

So if you add content/terms/etc. programmatically, Drupal's interior ID tracking system isn't aware of those.

---
http://jonahan.com