Summary: | Something wrong with databse update 3.09.00.044 | ||
---|---|---|---|
Product: | Koha | Reporter: | Katrin Fischer <katrin.fischer> |
Component: | Database | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P5 - low | CC: | m.de.rooy, magnus, veron |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Katrin Fischer
2012-09-14 08:22:23 UTC
I did an upgrade from .33 to .44 through the web installer earlier today and did not see this error: Upgrade to 3.09.00.033 done (Add OpacSuppressionByIPRange syspref) Upgrade to 3.09.00.034 done (Bug 8207: correct typo in authority types) Upgrade to 3.09.00.035 done (Adding PrefillItem and SubfieldsToUseWhenPrefill sysprefs) Upgrade to 3.09.00.036 done (Add colum agerestriction to biblioitems and deletedbiblioitems, add system preferences AgeRestrictionMarker and AgeRestrictionOverride) Upgrade to 3.09.00.037 done (creating `transport_cost` table; adding UseTransportCostMatrix systempref, in circulation) Upgrade to 3.09.00.038 done (Increase the maximum size of a borrower attribute value) Upgrade to 3.09.00.039 done (Add system preference DidYouMeanFromAuthorities) Upgrade to 3.09.00.040 done (Add IncludeSeeFromInSearches system preference) Upgrade to 3.09.00.041 done (Add system preference ExportRemoveFields) Upgrade to 3.09.00.042 done (Adds New System preference ExportWithCsvProfile) Upgrade to 3.09.00.043 done (Adding parent_ordernumber in aqorders) Upgrade done ( Added Collection Code to Statistics table. ) Everything went OK, update done. Katrin, I have this kind of errors if with columns I added before while developing. Searched through updatedatabase.pl, there is only one place where colum ccode is added to table statistics (while updating to version '3.09.00.044') I propose to set this bug to Resolved. Please reset it to NEW if you do not agree :-) Marc I am quite sure I never tested this specific development... but if noone else runs into this, it must be something in my database. |