I'm getting these error messages when running the update following the upgrade from 1.11 to 1.14 and I'm not sure how to fix them.

user warning: Incorrect table definition; there can be only one auto column and it must be defined as a key query: ALTER TABLE biblio_contributor_data DROP PRIMARY KEY in C:\Program Files\Apache Group\Apache2\htdocs\drupal6\includes\database.mysql-common.inc on line 386.

user warning: Multiple primary key defined query: ALTER TABLE biblio_contributor_data ADD PRIMARY KEY (cid, aka) in C:\Program Files\Apache Group\Apache2\htdocs\drupal6\includes\database.mysql-common.inc on line 374.

Any help greatly appreciated.

Bobb Menk
MIT Lincoln Laboratory Library

Comments

rjerome’s picture

rjerome commented

I'm not sure why you would be seeing that now since it would appear that warning is being generated in update 6018 which was introduced in version 6.x-1.3 of the module.

The only thing I can see is the addition of an argument to that update function (although that function should not be called if you were just going from 1.11 to 1.14).

Could you try changing line 1700 in biblio.install from...

function biblio_update_6018(&$sandbox) {

to this...

function biblio_update_6018() {

i.e. remove the "&$sandbox" argument.

bmenk’s picture

bmenk commented

Thanks for the quick response.

I removed the &$sandbox argument and re-ran update.php It ran without error, but I now find that the actual node pages are just blank displays. Is that likely to be related to this upgrade or am I looking at something else as the likely culprit?

Re 1.3 vs. 1.1 - I don't have any kind of versioning repository on this install and could only see the download for 1.1, but I may well have done an intermediary upgrade to 1.3 - sorry for the misinformation.

Thanks again.

Bobb

bmenk’s picture

bmenk commented

White screen was the fault of the Revisioning module upgrade, so I think I'm happy with Biblio.

Thanks

rjerome’s picture

rjerome commented
Status: Active » Fixed

Still not sure why you ran into that, but glad it's fixed :-)

Status: Fixed » Closed (fixed)

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