Convenient updates
Keep your installation up-to-date with the convenient update solution provided by ProjectForge.
- Language
-
Deutsche Version
- News
- 08/27/2010 Preview of Version 3.4
- 07/13/2010 Version 3.3.47 released
- 05/28/2010 Version 3.3.45 released
- 05/09/2010 PF at Google code
- 05/03/2010 English web site
- 04/30/2010 Easy to develop
- 04/25/2010 Maven repository
- 04/19/2010 projectforge.org BETA
- Quick links
- Home
- Demo system
- Downloads
- Micromata labs
Keep your installation up-to-date with the convenient update solution provided by ProjectForge.
Updates through simple clicks
ProjectForge provides a very convenient method for updating your ProjectForge installation. Select the menu "Update system" and then choose "check for updates". The site www.projectforge.org provides update scripts for your system (using https for security reasons).
Both the data base scheme and the migration of data base content will be updated automatically with scripts.
Update from version 3.3.47 to 3.4.0 (without update mechanism)
ALTER TABLE t_gantt_chart ADD COLUMN settings_as_xml VARCHAR(10000);
ALTER TABLE t_gantt_chart ADD COLUMN style_as_xml VARCHAR(10000);
ALTER TABLE t_gantt_chart ADD COLUMN gantt_objects_as_xml VARCHAR(10000);
ALTER TABLE t_gantt_chart ADD COLUMN read_access VARCHAR(16);
ALTER TABLE t_gantt_chart ADD COLUMN write_access VARCHAR(16);
ALTER TABLE t_gantt_chart ADD COLUMN owner_fk INT4;
ALTER TABLE t_gantt_chart ADD CONSTRAINT t_gantt_chart_owner_fk FOREIGN KEY (owner_fk) REFERENCES t_pf_user(pk);
ALTER TABLE t_task RENAME COLUMN duration_days TO duration;
ALTER TABLE t_task RENAME COLUMN gantt_dep_day_offset TO gantt_predecessor_offset;
ALTER TABLE t_task RENAME COLUMN gantt_dep_on_task_fk TO gantt_predecessor_fk;
ALTER TABLE t_task ADD COLUMN gantt_rel_type VARCHAR(15);
ALTER TABLE t_task DROP COLUMN gantt_dep_type;
Update from version 3.3.46 to 3.3.47 (without update mechanism)
CREATE TABLE t_gantt_chart (
pk INT4,
created TIMESTAMP,
last_update TIMESTAMP,
deleted BOOLEAN,
name VARCHAR(1000),
task_fk INT4,
PRIMARY KEY (pk),
FOREIGN KEY (task_fk) REFERENCES t_task(pk)
);
CREATE TABLE t_contract (
pk INT4,
created TIMESTAMP,
last_update TIMESTAMP,
deleted BOOLEAN,
number INT4,
c_date DATE,
valid_from DATE,
valid_until DATE,
title VARCHAR(1000),
co_contractor_a VARCHAR(1000),
contract_person_a VARCHAR(1000),
signer_a VARCHAR(1000),
co_contractor_b VARCHAR(1000),
contract_person_b VARCHAR(1000),
signer_b VARCHAR(1000),
signing_date DATE,
type VARCHAR(100),
status VARCHAR(100),
text VARCHAR(4000),
reference VARCHAR(1000),
filing VARCHAR(1000),
resubmission_on_date DATE,
due_date DATE,
PRIMARY KEY (pk)
);
ALTER TABLE t_contract ADD CONSTRAINT t_contract_uniq UNIQUE (number);
ALTER TABLE t_task ADD COLUMN workpackage_code VARCHAR(100);
ALTER TABLE t_task ADD COLUMN gantt_type VARCHAR(10);
ALTER TABLE t_task ADD COLUMN duration_days DECIMAL(10, 5);
ALTER TABLE t_task ADD COLUMN gantt_dep_type CHAR(2);
ALTER TABLE t_task ADD COLUMN gantt_dep_day_offset INT4;
ALTER TABLE t_task ADD COLUMN gantt_dep_on_task_fk INT4;
ALTER TABLE t_task ADD CONSTRAINT t_task_gantt_dep_on_task_fk FOREIGN KEY (gantt_dep_on_task_fk) REFERENCES t_task(pk);
ALTER TABLE t_task DROP CONSTRAINT t_task_parent_task_id_key;
ALTER TABLE t_task RENAME COLUMN name TO title;
ALTER TABLE t_task RENAME COLUMN resumption TO start_date;
ALTER TABLE t_task RENAME COLUMN deadline TO end_date;
ALTER TABLE t_task DROP COLUMN from_date;
ALTER TABLE t_task ADD CONSTRAINT t_task_parent_task_id_key UNIQUE (parent_task_id, title);
ALTER TABLE t_pf_user ADD COLUMN jira_username VARCHAR(100);
ALTER TABLE t_imported_meb_entry ADD COLUMN source VARCHAR(10);
ALTER TABLE t_group_task_access ADD COLUMN recursive BOOLEAN NOT NULL DEFAULT(true);
DROP INDEX idx_fk_t_task_kost2_id;
DROP INDEX idx_fk_t_task_projekt_id;
DROP INDEX idx_fk_t_task_old_kost2_id;
DROP INDEX idx_fk_t_task_old_projekt_id;
Update from version 3.3.44 to 3.3.45 (without update mechanism)
ALTER TABLE t_pf_user ADD COLUMN personal_meb_identifiers VARCHAR(255);
CREATE TABLE t_meb_entry (
pk INT4,
created TIMESTAMP,
last_update TIMESTAMP,
deleted BOOLEAN,
sender VARCHAR(255) NOT NULL,
title VARCHAR(255),
origin_message VARCHAR(4000) NOT NULL,
message VARCHAR(4000),
date TIMESTAMP NOT NULL,
status VARCHAR(20) NOT NULL,
owner_fk INT4,
PRIMARY KEY (pk),
FOREIGN KEY (owner_fk) REFERENCES t_pf_user(pk)
);
ALTER TABLE t_meb_entry ADD CONSTRAINT t_mep_entry_uniq UNIQUE (owner_fk, sender, date, origin_message);
CREATE TABLE t_imported_meb_entry (
pk INT4,
created TIMESTAMP,
last_update TIMESTAMP,
deleted BOOLEAN,
sender VARCHAR(255) NOT NULL,
check_sum VARCHAR(255) NOT NULL,
date TIMESTAMP NOT NULL,
PRIMARY KEY (pk)
);
Update from version 3.3.43 to 3.3.44 (without update mechanism)
drop table t_user_right;
create table t_user_right (
pk int4 not null,
created timestamp,
deleted boolean not null,
last_update timestamp,
right_id varchar(40),
value varchar(40),
user_fk int4 not null,
primary key (pk),
foreign key (user_fk) references t_pf_user(pk)
);
alter table t_user_right add constraint t_user_right_user_fk_key unique (user_fk, right_id);