covers versions 3.12.7 stable, 3.14.3 stable, 3.16.0 RC1, 3.17.0 development
There is no general MySource Matrix developer news this week.
Added to: 3.17.0 development
The performance of the lookup values system - used for determining the appropriate design and/or paint layout for a page - has been improved considerably. Preliminary testing has seen the number of queries required for getting design or paint layout information reduced by an average of 50pc.
No new generic features are currently scheduled for development.
Additional queries:
These queries are required to move existing development systems to the new lookup value system.
Before running, and before updating your code, please ensure that rollback has been disabled. Please see the Rollback Management Guide for information on how to do this.
Once rollback is disabled, update your code base, then run these queries:
DELETE FROM sq_ast_lookup_value
WHERE inhd = 1;
ALTER TABLE sq_ast_lookup_value
DROP COLUMN inhd;
ALTER table sq_ast_lookup_value ADD COLUMN depth integer;
CREATE INDEX sq_ast_lookup_value_depth ON sq_ast_lookup_value (depth);
UPDATE sq_ast_lookup_value
SET url = url
||'/'
WHERE url IN (SELECT url
FROM sq_ast_lookup_value lv
WHERE lv.url IN (SELECT url
FROM sq_ast_lookup l
WHERE l.assetid IN (SELECT majorid
FROM sq_ast_lnk
WHERE value LIKE 'override::%')));
UPDATE sq_ast_lookup_value
SET depth = l.depth
FROM (SELECT url, (length(url) - length(replace(url, '/', ''))) as depth FROM sq_ast_lookup_value) AS l
WHERE sq_ast_lookup_value.url = l.url;
ALTER table sq_ast_lookup_value ALTER COLUMN depth SET NOT NULL;
ALTER TABLE sq_rb_ast_lookup_value
DROP COLUMN inhd;
ALTER table sq_rb_ast_lookup_value ADD COLUMN depth integer;
CREATE INDEX sq_rb_ast_lookup_value_depth ON sq_rb_ast_lookup_value (depth);
DELETE FROM sq_ast_lookup_value
WHERE inhd = 1;
ALTER TABLE sq_ast_lookup_value
DROP COLUMN inhd;
ALTER table sq_ast_lookup_value ADD depth integer;
CREATE INDEX sq_ast_lookup_value_depth ON sq_ast_lookup_value (depth);
UPDATE sq_ast_lookup_value
SET url = url
||'/'
WHERE url IN (SELECT url
FROM sq_ast_lookup_value lv
WHERE lv.url IN (SELECT url
FROM sq_ast_lookup l
WHERE L.assetid IN (SELECT majorid
FROM sq_ast_lnk
WHERE value LIKE 'override::%')));
UPDATE sq_ast_lookup_value lv
SET lv.depth = (SELECT (LENGTH(url) - LENGTH(REPLACE(url,'/',''))) AS depth
FROM sq_ast_lookup_value L
WHERE lv.url = l.url
AND ROWNUM = 1);
ALTER table sq_ast_lookup_value MODIFY depth NOT NULL;
ALTER TABLE sq_rb_ast_lookup_value
DROP COLUMN inhd;
ALTER table sq_rb_ast_lookup_value ADD depth integer;
CREATE INDEX sq_rb_ast_lookup_value_depth ON sq_rb_ast_lookup_value (depth);
After running, remember to turn rollback back on, if you had to disable it previously. Again, please consult the Rollback Management Guide for the procedure.
Additional comments: No additional upgrade steps are required.
| Bug ID | 3.12.x | 3.14.x | 3.16.x | Dev | Description |
| 2581 | Y | Y | Y | Y | Related Listing nested content recursion warning |
| 2586 | N | Y | N | N | WYSIWYG design styles lost on commit |
| 2588 | N | Y | N | N | Asset Map boundary error (not confirmed) |
| 2589 | Y | Y | Y | Y | Asset_Manager:::getLinkByAsset() function returns odd results with shadow assets and force_array=TRUE |
Bug #2564 ("CSS File asset's cached File asset getting the wrong URL", reported by Christophe Olivar on August 3rd) was marked as Can Not Replicate after both the original reporter and another developer was unable to reproduce on PostgreSQL and Oracle systems.
| Bug ID | Description |
| 2582 | Script to check file versioning info on the filesystem |
| 2583 | Allow "levels to print" in asset lineage on design customization |
| 2584 | Form Contents/Questions getting metadata/workflow |
| 2587 | Option to not use tables in Image Content Type |
| 2590 | User is presented with unwieldy list of errors when someone else has the lock on details screen |
| Bug ID | 3.12.x | 3.14.x | 3.16.x | Dev | Description |
| 2589 | Y | Y | Y | Y | Asset_Manager:::getLinkByAsset() function returns odd results with shadow assets and force_array=TRUE |
There are currently no comments for this newsletter.