- Edited
Hi everyoneI read that the errors in the database upgrade from version 1.8 to 1.9 is not a concern, but I installed from scratch too and compare schemes of both databases and have several differences. Should I worry about?
Hi everyoneI read that the errors in the database upgrade from version 1.8 to 1.9 is not a concern, but I installed from scratch too and compare schemes of both databases and have several differences. Should I worry about?
Can you be more specific about what differences you are seeing?
Yes, this is the sync script of database from scratch vs. database upgrade from 1.8.1.2 to 1.9:---- Disable foreign keys--/*!40014 SET @[deleted]=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;SET NAMES 'utf8';USE osticket;DELIMITER $$---- Drop procedure "etickettoosticket"--DROP PROCEDURE IF EXISTS etickettoosticket$$DELIMITER ;---- Drop table "ost_ticket__cdata"--DROP TABLE ost_ticket__cdata;---- Alter table "ost_file"--ALTER TABLE ost_file DROP INDEX hash, CHANGE COLUMN size size BIGINT(20) UNSIGNED NOT NULL DEFAULT 0, CHANGE COLUMN `key` `key` VARCHAR(86) CHARACTER SET ascii COLLATE ascii_general_ci NOT NULL, CHANGE COLUMN signature signature VARCHAR(86) BINARY CHARACTER SET ascii COLLATE ascii_bin NOT NULL;ALTER TABLE ost_file ADD INDEX `key` (`key`);---- Alter table "ost_help_topic"--ALTER TABLE ost_help_topic CHANGE COLUMN form_id form_id INT(10) UNSIGNED NOT NULL DEFAULT 0 AFTER page_id;---- Alter table "ost_plugin"--ALTER TABLE ost_plugin ADD COLUMN version VARCHAR(64) DEFAULT NULL AFTER isactive;---- Alter table "ost_ticket"--ALTER TABLE ost_ticket DROP INDEX email_extid, CHANGE COLUMN number number VARCHAR(20) DEFAULT NULL AFTER ticket_id;---- Alter table "ost_user"--ALTER TABLE ost_user CHANGE COLUMN org_id org_id INT(10) UNSIGNED NOT NULL;---- Enable foreign keys--/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
Sorry, the procedure "etickettoosticket" is a procedure created by me, ignore that one