From: Jun Y. <ju...@ca...> - 2007-01-18 04:09:16
|
Hi, Here is the db model change that I have seen from RC1 to RC2 in case someone is also upgrading like us. -- upgrade script for 1.3 RC1 (SVN 431) to 1.3 RC2 (SVN 449) ALTER TABLE `%TABLE_PREFIX%author_org_structure` ADD COLUMN `auo_assessed_year` varchar(11) default NULL, ADD UNIQUE KEY `support_unique_key` (`auo_org_id`,`auo_aut_id`,`auo_cla_id`,`auo_fun_id`), default CHARACTER SET utf8; ALTER TABLE `%TABLE_PREFIX%user` ADD FULLTEXT KEY `usr_fulltext` (`usr_full_name`,`usr_given_names`,`usr_family_name`,`usr_username`,`usr_shib_username`); I did notice some strange things about /setup/schema.sql. 1. on schema.sql news.nws_title is a unique key. Do we really want to make this column unique? 2. These indexes are not present on schema.sql KEY `rmf_varchar_combo` (`rmf_xsdmf_id`,`rmf_varchar`), KEY `combo_pid_num_xsdmf_int` (`rmf_rec_pid_num`,`rmf_xsdmf_id`,`rmf_int`), They seem to be present on upgrade.sql 3. I only noticed this on my RC2 merge, it seems some tables are using latin1 encoding. This is still true with current RC2 schema.sql Thanks. Jun |
From: Christiaan K. <c.k...@li...> - 2007-01-18 05:21:35
|
Hi Jun Thanks for picking those up.=20 1. No nws_title probablys shouldn't be unique. I think that was a carry-over from Eventum. 2. We will add those in a commit soon. 3. There are a few areas where latin1 is still necessary as utf8 will prevent some of the indexes from being able to be created (too big thanks to utf8 chars being bigger than latin1) but this should be rare and minimal. Cheers, Christiaan -----Original Message----- From: fez...@li... [mailto:fez...@li...] On Behalf Of Jun Yamog Sent: Thursday, 18 January 2007 2:07 PM To: fez...@li... Subject: [Fez-developers] upgrading from 1.3 rc1 to 1.3 rc2 Hi, Here is the db model change that I have seen from RC1 to RC2 in case someone is also upgrading like us. -- upgrade script for 1.3 RC1 (SVN 431) to 1.3 RC2 (SVN 449) ALTER TABLE `%TABLE_PREFIX%author_org_structure` ADD COLUMN `auo_assessed_year` varchar(11) default NULL, ADD UNIQUE KEY `support_unique_key` (`auo_org_id`,`auo_aut_id`,`auo_cla_id`,`auo_fun_id`), default CHARACTER SET utf8; ALTER TABLE `%TABLE_PREFIX%user` ADD FULLTEXT KEY `usr_fulltext` (`usr_full_name`,`usr_given_names`,`usr_family_name`,`usr_username`,`usr _shib_username`); I did notice some strange things about /setup/schema.sql. 1. on schema.sql news.nws_title is a unique key. Do we really want to make this column unique? 2. These indexes are not present on schema.sql KEY `rmf_varchar_combo` (`rmf_xsdmf_id`,`rmf_varchar`), KEY `combo_pid_num_xsdmf_int` (`rmf_rec_pid_num`,`rmf_xsdmf_id`,`rmf_int`), They seem to be present on upgrade.sql 3. I only noticed this on my RC2 merge, it seems some tables are using latin1 encoding. This is still true with current RC2 schema.sql Thanks. Jun ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Fez-developers mailing list Fez...@li... https://lists.sourceforge.net/lists/listinfo/fez-developers |