Hi Bruce,
I've finished the upgrade,
Working with postgres, from 2.0.3 (tarball)) to 2.1.0b2 (oacs-5-1)
dotlrn:
tcl/apm-callback-procs.tcl
I changed the apm_upgrade_logic from 2.0.3 2.1.0 to 2.0.3 2.1.0b2
file-storage:
upgrade-5.1.0d1-5.1.0d2.sql
The script did not work, i commented this line:
line 49
-- drop function file_storage__new_root_folder(integer);
This line was a problem for me because i did not have the
function file_storage__new_root_folder(integer) so i don`t
know if i should commit this change.
workflow:
upgrade-1.2-2.0d1.sql
I had a problem with this script because it alters a table:
alter table workflow_fsm_action_en_in_st add constraint
workflow_fs_action_en_in_st_pk primary key (action_id, state_id);
The instruction crash because i had duplicate rows, I deleted the
rows,
delete from workflow_fsm_action_en_in_st where action_id='4'; ...
Check the table before running the script.
file-storage:
upgrade-5.1.0a6-5.1.0a7.sql
I had a problem with a constraint, but it was a problem with a
row in my system, i searched the row and change a title.
static-portlet:
upgrade-2.0.3d1-2.0.3d2.sql
This script was not run in the upgrade, check if it is in the
list of scripts to run, if not run it manually after the upgrade.
psql -f
packages/static-portlet/sql/postgresql/upgrade/upgrade-2.0.3d1-2.0.3d2.sql ....
These were my troubles, if you have a problem with a script it
will be because a row in your system or a constraint.
See your table and modify or delete rows.
I did the upgrade for two sites, form 2.0.3 to 2.1.0a2 / 2.1.0b2
You can use the tarball beta 2.1.0b1 or a checkout from oacs-5-1
Best Regards,
Héctor.
