MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 38
Friday 26th August 2005

covers versions 3.4.5 stable, 3.6.0 RC2, 3.7.0 development

News

Important Upgrade For Triggers

The triggering system of MySource Matrix uses the sq_trig_hash table to cache out various config information that speeds up the processes of looking for triggers that need executing when an action is performed. This table did not have a primary key defined. This weeks upgrades for 3.6.x and 3.7.x provide a query to add a primary key to the sq_trig_hash table.

The primary key query will fail if you currently have triggers configured within your system. The existing NULL values will stop the primary key from being applied. To be able to apply the primary key, first recommit each trigger defined within your system. This will replace the NULL fields and allow the primary key to be applied.

Changes To Unrestricted Access

A change was made to 3.6.x and 3.7.x a while ago so that all user groups have unrestricted screen access applied by default. If unrestricted access had not been granted, restrictions were in place. This logic has now been changed so that unrestricted access is granted if no restrictions are in place. This makes the setting of unrestricted access obsolete. A query is included in this week's upgrade to remove the unrestricted access database entires as they are no longer checked.

New Features

Ability To Delete Form Submissions

Added to: 3.7.0 development

Custom form submissions can now be deleted from the Form Submissions screen. Individual form submissions can be deleted and a checkbox is provided to delete all form submissions displayed on the screen. Deleted form submissions are placed in the Trash so they can be recovered if required.

Improved Recreate Link Tree Script

Added to: 3.6.0 RC2, 3.7.0 development

A new version of the recreate_link_tree.php script has been added to MySource Matrix last week. The old script was using asset manager getLinks() calls. This was very, very slow and actually had problems because the form_email asset is a bridge and only returns TYPE_2 links, which meant all the form submissions in the systems not having entries in the link tree table.

The new version of the script does what the original one used to but reads directly from the sq_ast_lnk table, making it much quicker and using much less memory.

The biggest change to this script is that it now does NOT run the insert queries. It just sends them to STDOUT. If you are using PostgreSQL, the script will output the queries in COPY format because pgsql inserts much quicker with that.

Usage: php scripts/recreate_link_tree.php . > tmp.sql

Upgrading

3.6.0 Rc2

Run step_02.php: no
Run step_03.php: yes
Run compile_locale.php: yes

Additional queries:

[PostgreSQL] 
ALTER TABLE sq_file_vers_history ALTER COLUMN md5 DROP NOT NULL;
ALTER TABLE sq_file_vers_history ALTER COLUMN sha1 DROP NOT NULL;

[Oracle]
ALTER TABLE sq_file_vers_history MODIFY md5 CHAR(32) NULL;
ALTER TABLE sq_file_vers_history MODIFY sha1 CHAR(40) NULL;

DELETE FROM sq_ast_edit_access WHERE type_code = 0 AND screen = 0 AND section = 0;

ALTER TABLE sq_trig_hash ADD CONSTRAINT sq_trig_hash_pkey PRIMARY KEY( event, assetid, asset_type, treeid, tree_propagate, triggerid, parentid, parent_type, childid, child_type );

Additional comments: If you have any triggers in your system you will need to recommit the trigger details for each one before you can add the primary key constraint.

3.7.0 Development

Run step_02.php: no
Run step_03.php: yes
Run compile_locale.php: yes

Additional queries:

[PostgreSQL]
ALTER TABLE sq_file_vers_history ALTER COLUMN md5 DROP NOT NULL;
ALTER TABLE sq_file_vers_history ALTER COLUMN sha1 DROP NOT NULL;

[Oracle]
ALTER TABLE sq_file_vers_history MODIFY md5 CHAR(32) NULL;
ALTER TABLE sq_file_vers_history MODIFY sha1 CHAR(40) NULL;

DELETE FROM sq_ast_edit_access WHERE type_code = 0 AND screen = 0 AND section = 0;

ALTER TABLE sq_trig_hash ADD CONSTRAINT sq_trig_hash_pkey PRIMARY KEY( event, assetid, asset_type, treeid, tree_propagate, triggerid, parentid, parent_type, childid, child_type );

Additional comments: If you have any triggers in your system you will need to recommit the trigger details for each one before you can add the primary key constraint.

New Bugs Added To Bug Tracker

New Feature Requests Added To Bug Tracker

Bugs Fixed In The Bug Tracker

View Comments