vtiger

[jonb]

I just ran the migration script on my old 4.2-p1 install to upgrade to 5.0.3 and received the following query errors.

Code: alter table vtiger_user2role drop FOREIGN KEY fk_user2role2
ALTER TABLE vtiger_user2role ADD CONSTRAINT fk_user2role2 FOREIGN KEY (roleid) REFERENCES vtiger_role(roleid) ON DELETE CASCADE
alter table vtiger_leadgrouprelation drop FOREIGN KEY fk_leadgrouprelation2
alter table vtiger_activitygrouprelation drop FOREIGN KEY fk_activitygrouprelation2
alter table vtiger_ticketgrouprelation drop FOREIGN KEY fk_ticketgrouprelation2
INSERT INTO vtiger_tab VALUES(26,'Campaigns',0,23,'Campaigns',null,null,1)
insert into vtiger_moduleowners values(,1)
insert into vtiger_profile2standardpermissions values(1,26,0,0)
insert into vtiger_profile2standardpermissions values(1,26,1,0)
insert into vtiger_profile2standardpermissions values(1,26,2,0)
insert into vtiger_profile2standardpermissions values(1,26,3,0)
insert into vtiger_profile2standardpermissions values(1,26,4,0)
insert into vtiger_profile2standardpermissions values(2,26,0,0)
insert into vtiger_profile2standardpermissions values(2,26,1,0)
insert into vtiger_profile2standardpermissions values(2,26,2,0)
insert into vtiger_profile2standardpermissions values(2,26,3,0)
insert into vtiger_profile2standardpermissions values(2,26,4,0)
insert into vtiger_profile2standardpermissions values(3,26,0,0)
insert into vtiger_profile2standardpermissions values(3,26,1,0)
insert into vtiger_profile2standardpermissions values(3,26,2,0)
insert into vtiger_profile2standardpermissions values(3,26,3,0)
insert into vtiger_profile2standardpermissions values(3,26,4,0)
insert into vtiger_profile2standardpermissions values(4,26,0,0)
insert into vtiger_profile2standardpermissions values(4,26,1,0)
insert into vtiger_profile2standardpermissions values(4,26,2,0)
insert into vtiger_profile2standardpermissions values(4,26,3,0)
insert into vtiger_profile2standardpermissions values(4,26,4,0)
ALTER TABLE vtiger_parenttabrel ADD CONSTRAINT fk_2_vtiger_parenttabrel FOREIGN KEY (parenttabid) REFERENCES vtiger_parenttab(parenttabid) ON DELETE CASCADE

Any input on what might cause problems in the future would be much appreciated. I'm guessing for the most part that they don't really matter, but I figured I'd ask anyway. Thanks for the great release guys :)

[Galactic Dominator]

you posted echoed sql statements, not errors.

[jonb]

Galactic Dominator wrote: you posted echoed sql statements, not errors.

Sorry about that, I used a bad choice of words. What I meant to say is that the migration script reported that there were errors on the above queries and that they were not executed properly. My question is that if the above queries do not execute properly, will I have issues in the future? Thanks for letting me clear that up. Sorry.

[dina]

Hi,

We are not providing migration from v4.2.p1 to v5.0.3.
We are supporting migration from v4.2.3 to v5.0.3 and v4.2.p2 to v5.0.3.
So kindly migrate your system to v4.2.3 or v4.2.p2 and then you can use the migration wizard available in v5.0.3 to migrate your code.


Hope i am clear,Please contact us for further informations.

Thanks & Regards,
Dina.

[jonb]

I patched to 4.2-p2 and still had the same error listing....in case it might help someone else, here's the file I'm using to finish off the queries it's having problems with....

Code: -- This tries to drop a key that doesn't exist anyway
-- alter table vtiger_user2role drop FOREIGN KEY fk_user2role2;

-- These should run fine *after* the migration is complete, they need to be run manually.
ALTER TABLE vtiger_user2role ADD CONSTRAINT fk_user2role2 FOREIGN KEY (roleid) REFERENCES vtiger_role(roleid) ON DELETE CASCADE;
alter table vtiger_leadgrouprelation drop FOREIGN KEY fk_leadgrouprelation2;
alter table vtiger_activitygrouprelation drop FOREIGN KEY fk_activitygrouprelation2;
alter table vtiger_ticketgrouprelation drop FOREIGN KEY fk_ticketgrouprelation2;

-- The following query needs to be modified to include the customized flag
-- Change the following query:
-- INSERT INTO vtiger_tab VALUES(26,'Campaigns',0,23,'Campaigns',null,null,1)
-- To be the following:
INSERT INTO vtiger_tab VALUES(30,'Campaigns',0,23,'Campaigns',0,0,0,1);
-- Then run the query manually after the migration

-- We can ignore this one and just assign who owns the module later
-- Without this run, everything is owned by admin, and that's ok
-- insert into vtiger_moduleowners values(,1)

-- This sets permissions of the above Campaigns tab
-- The following queries:
-- insert into vtiger_profile2standardpermissions values(1,26,0,0)
-- insert into vtiger_profile2standardpermissions values(1,26,1,0)
-- insert into vtiger_profile2standardpermissions values(1,26,2,0)
-- insert into vtiger_profile2standardpermissions values(1,26,3,0)
-- insert into vtiger_profile2standardpermissions values(1,26,4,0)
-- insert into vtiger_profile2standardpermissions values(2,26,0,0)
-- insert into vtiger_profile2standardpermissions values(2,26,1,0)
-- insert into vtiger_profile2standardpermissions values(2,26,2,0)
-- insert into vtiger_profile2standardpermissions values(2,26,3,0)
-- insert into vtiger_profile2standardpermissions values(2,26,4,0)
-- insert into vtiger_profile2standardpermissions values(3,26,0,0)
-- insert into vtiger_profile2standardpermissions values(3,26,1,0)
-- insert into vtiger_profile2standardpermissions values(3,26,2,0)
-- insert into vtiger_profile2standardpermissions values(3,26,3,0)
-- insert into vtiger_profile2standardpermissions values(3,26,4,0)
-- insert into vtiger_profile2standardpermissions values(4,26,0,0)
-- insert into vtiger_profile2standardpermissions values(4,26,1,0)
-- insert into vtiger_profile2standardpermissions values(4,26,2,0)
-- insert into vtiger_profile2standardpermissions values(4,26,3,0)
-- insert into vtiger_profile2standardpermissions values(4,26,4,0)
insert into vtiger_profile2standardpermissions values(1,30,0,0);
insert into vtiger_profile2standardpermissions values(1,30,1,0);
insert into vtiger_profile2standardpermissions values(1,30,2,0);
insert into vtiger_profile2standardpermissions values(1,30,3,0);
insert into vtiger_profile2standardpermissions values(1,30,4,0);
insert into vtiger_profile2standardpermissions values(2,30,0,0);
insert into vtiger_profile2standardpermissions values(2,30,1,0);
insert into vtiger_profile2standardpermissions values(2,30,2,0);
insert into vtiger_profile2standardpermissions values(2,30,3,0);
insert into vtiger_profile2standardpermissions values(2,30,4,0);
insert into vtiger_profile2standardpermissions values(3,30,0,0);
insert into vtiger_profile2standardpermissions values(3,30,1,0);
insert into vtiger_profile2standardpermissions values(3,30,2,0);
insert into vtiger_profile2standardpermissions values(3,30,3,0);
insert into vtiger_profile2standardpermissions values(3,30,4,0);
insert into vtiger_profile2standardpermissions values(4,30,0,0);
insert into vtiger_profile2standardpermissions values(4,30,1,0);
insert into vtiger_profile2standardpermissions values(4,30,2,0);
insert into vtiger_profile2standardpermissions values(4,30,3,0);
insert into vtiger_profile2standardpermissions values(4,30,4,0);

-- This should run fine *after* the migration is complete, it needs to be run manually.
ALTER TABLE vtiger_parenttabrel ADD CONSTRAINT fk_2_vtiger_parenttabrel FOREIGN KEY (parenttabid) REFERENCES vtiger_parenttab(parenttabid) ON DELETE CASCADE;

-Jon