| .. |
|
portal
|
81cac08849
N.434 Optimized the DB queries. As an example, the query that shows the service catalog in the enhanced customer portal is now made of 5 nodes (at the class level) whereas it used to be made of 11 nodes... for the exact same results. This optimization impacts almost each queries built by iTop. The expected benefit can insignificant or not, depending on the cardinality of the data, the datamodel and the original OQL queries. We found one case where the query execution would apparently never end and it takes now less than a second. The risk with such a change is that is affects most of the queries built by iTop -requires testing!
|
9 years ago |
|
cs.dict.itop-portal-base.php
|
41ad21df38
#1281 Portal : Fixed a few hardcoded strings to dictionnaries
|
9 years ago |
|
en.dict.itop-portal-base.php
|
41ad21df38
#1281 Portal : Fixed a few hardcoded strings to dictionnaries
|
9 years ago |
|
fr.dict.itop-portal-base.php
|
bfee62379d
Customer portal : User Profile brick that allows basic Contact informations edition, password / preferences change from the portal
|
9 years ago |
|
module.itop-portal-base.php
|
bac79f6e30
Increased version number of the module to 1.0.1 to reflect the change related to revision 4300 (support of custom controller in a brick).
|
9 years ago |
romainq
81cac08849
N.434 Optimized the DB queries. As an example, the query that shows the service catalog in the enhanced customer portal is now made of 5 nodes (at the class level) whereas it used to be made of 11 nodes... for the exact same results. This optimization impacts almost each queries built by iTop. The expected benefit can insignificant or not, depending on the cardinality of the data, the datamodel and the original OQL queries. We found one case where the query execution would apparently never end and it takes now less than a second. The risk with such a change is that is affects most of the queries built by iTop -requires testing!