Bug 14411 - items.itemnotes_nonpublic not created during upgrade
Summary: items.itemnotes_nonpublic not created during upgrade
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Installation and upgrade (command-line installer) (show other bugs)
Version: 3.20
Hardware: Other Linux
: P5 - low normal (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-18 15:21 UTC by jaker@mvwsd.org
Modified: 2016-06-21 21:37 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jaker@mvwsd.org 2015-06-18 15:21:10 UTC
I recently upgraded our Koha install to 3.20 using the Debian packages. During the upgrade I received the following message:

Please check each of your frameworks to ensure your non-public item notes are mapped to items.itemnotes_nonpublic. After doing so please have your administrator run misc/batchRebuildItemsTables.pl)

Which seems pretty straightforward, however, the itemnotes_nonpublic field does not exist in my items table. I also receive a template error when checking out an item. Manually creating the itemnotes_nonpublic column resolves the template error on checkout.

I upgraded two different servers and the column was not created on either server. I did have some problems with the items table during the upgrade. It was related to the change to the utf8_unicode collation so I am not sure if the field was not created in my items table because of those errors. I did not see any errors related to the itemnotes_nonpublic column during the upgrade.

Also, I upgraded from 3.16 directly to 3.20 and I am running Debian Jessie

It may be just an issue with my install but I wanted to report it in case it was a widespread issue.
Comment 1 Tomás Cohen Arazi 2015-06-18 15:45:47 UTC
I think this one is INVALID because you can see that updatedatabase.pl (the script run during upgrade) includes the following lines:

$DBversion = '3.19.00.027';
if ( CheckVersion($DBversion) ) {
    $dbh->do("ALTER TABLE items ADD COLUMN itemnotes_nonpublic MEDIUMTEXT AFTER itemnotes");
    $dbh->do("ALTER TABLE deleteditems ADD COLUMN itemnotes_nonpublic MEDIUMTEXT AFTER itemnotes");
    print "Upgrade to $DBversion done (Bug 4222: Nonpublic note not appearing in the staff client) <b>Please check each of your frameworks to ensure your non-public item notes are mapped to items.itemnotes_nonpublic. After doing so please have your administrator run misc/batchRebuildItemsTables.pl </b>)\n";
    SetVersion($DBversion);
}

So your DB failed to have those columns added.
Comment 2 jaker@mvwsd.org 2015-06-18 15:54:49 UTC
Thanks. It must have failed on my install due to the problems I had with the UTF8 conversion of the item table. I checked my deleteditems table and it does have that field.