[Koha-bugs] [Bug 4310] No Migration for budgets from 3.0 to 3.2

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Sep 3 22:11:21 CEST 2010


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4310

--- Comment #8 from Colin Campbell <colin.campbell at ptfs-europe.com> 2010-09-03 20:11:20 UTC ---
I created a table holding the info needed for mapping:

CREATE TABLE fundmapping AS SELECT aqorderbreakdown.ordernumber, branchcode,
bookfundid, budgetdate, entrydate from aqorderbreakdown
join aqorders on aqorderbreakdown.ordernumber = aqorders.ordernumber;
ALTER TABLE fundmapping modify column bookfundid varchar(30);
ALTER TABLE fundmapping add column aqbudgetid integer;
CREATE INDEX fundmaporder ON fundmapping (ordernumber);
CREATE INDEX fundmapid ON fundmapping (bookfundid);
UPDATE fundmapping set budgetdate = entrydate where budgetdate IS NULL;
UPDATE fundmapping set budgetdate = entrydate where budgetdate = '0000-00-00';

and used that however the approach I'm now using is to recreate the budget data
and then use this to map, treating it as a data conversion task. This may be
problem made worse by nature of the data, but I rthink we need major warnings
for anyone running 3.0 Acq

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the Koha-bugs mailing list