Had an interesting bug come up with a large enterprise Drupal site where nodewords were failing to save only on newer articles.

Tracked this back to nodewords storing id as an unsigned tinyint(5), which maxes out at 65535. This is incongruous with the node table which uses an int(10) to store nids, so we end up with a case where any site that has nids higher than 65535 is unable to store nodewords data for those nodes.

Is there a particular reason for using tinyint? Altering the schema to redefine nodewords.item to an int(10) column worked as a fix for us.

Comments

entendu’s picture

entendu commented
Status: Active » Fixed

Ran into the same problem as you. This is fixed with an update hook in the dev version.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

preper’s picture

preper commented

I have the same problem about nodewords node number. I have nodes over 70.000 and I can not insert new content with metatags.

As you said I have upgrade to the dev version but it gives some errors. Then I have changed the mysql table of nodewords id type from SHORTINT(5) to INT(10).

Does this change cause a problem on mysql or drupal site? Is this change only the capacity of the table? I wonder if ti can cause problems in the future on other things?