MySQL CHECK TABLE

Previous topic

Developer

Next topic

Author	Message
Francisca Hernández	Thursday 19 July 2007 1:39:32 am Hi, i used to work with postgresql but i did a project with mysql to improve performace of site. i run CHECK TABLE and i see this warnings: Problems with indexes of table `ezcontentobject_attribute` - PRIMARY and INDEX keys should not both be set for column `id` - More than one INDEX key was created for column `contentobject_id` Problems with indexes of table `ezcontentobject_name` - PRIMARY and INDEX keys should not both be set for column `contentobject_id` Problems with indexes of table `ezenumobjectvalue` - PRIMARY and INDEX keys should not both be set for column `contentobject_attribute_id` Problems with indexes of table `ezkeyword` - More than one INDEX key was created for column `keyword` Problems with indexes of table `ezkeyword_attribute_link` - More than one INDEX key was created for column `keyword_id` Problems with indexes of table `eznode_assignment` - More than one INDEX key was created for column `contentobject_id` this is a problem for ezp performance? anyone can help me? thanks, fran Iguana IT, SL - http://www.iguanait.com
Rebecca Strozier	Wednesday 09 July 2008 6:21:11 am I am using MySQL (version 5.0.22) with ezPublish 4.0 and I get the same warning messages regarding indexes using the same columns for the tables below: Problems with indexes of table `ezcontentobject_attribute` PRIMARY and INDEX keys should not both be set for column `id` More than one INDEX key was created for column `contentobject_id` Problems with indexes of table `ezcontentobject_name` PRIMARY and INDEX keys should not both be set for column `contentobject_id` Problems with indexes of table `ezenumobjectvalue` PRIMARY and INDEX keys should not both be set for column `contentobject_attribute_id` Problems with indexes of table `ezkeyword` More than one INDEX key was created for column `keyword` Problems with indexes of table `ezkeyword_attribute_link` More than one INDEX key was created for column `keyword_id` Problems with indexes of table `eznode_assignment` More than one INDEX key was created for column `contentobject_id` Problems with indexes of table `ezurlalias_ml` PRIMARY and INDEX keys should not both be set for column `parent` More than one INDEX key was created for column `parent` More than one INDEX key was created for column `text` More than one INDEX key was created for column `action` More than one INDEX key was created for column `action_type` I believe MySQL will ignore the redundant indexes, however perhaps a review of the schema would be advisable.

Author

Message

Francisca Hernández

Thursday 19 July 2007 1:39:32 am

Hi,

i used to work with postgresql but i did a project with mysql to improve performace of site.
i run CHECK TABLE and i see this warnings:

Problems with indexes of table `ezcontentobject_attribute`
- PRIMARY and INDEX keys should not both be set for column `id`
- More than one INDEX key was created for column `contentobject_id`

Problems with indexes of table `ezcontentobject_name`
- PRIMARY and INDEX keys should not both be set for column `contentobject_id`

Problems with indexes of table `ezenumobjectvalue`
- PRIMARY and INDEX keys should not both be set for column `contentobject_attribute_id`

Problems with indexes of table `ezkeyword`
- More than one INDEX key was created for column `keyword`

Problems with indexes of table `ezkeyword_attribute_link`
- More than one INDEX key was created for column `keyword_id`

Problems with indexes of table `eznode_assignment`
- More than one INDEX key was created for column `contentobject_id`

this is a problem for ezp performance?
anyone can help me?

thanks, fran

Iguana IT, SL - http://www.iguanait.com

Rebecca Strozier

Wednesday 09 July 2008 6:21:11 am

I am using MySQL (version 5.0.22) with ezPublish 4.0 and I get the same warning messages regarding indexes using the same columns for the tables below:

Problems with indexes of table `ezcontentobject_attribute`
PRIMARY and INDEX keys should not both be set for column `id`
More than one INDEX key was created for column `contentobject_id`

Problems with indexes of table `ezcontentobject_name`
PRIMARY and INDEX keys should not both be set for column `contentobject_id`

Problems with indexes of table `ezenumobjectvalue`
PRIMARY and INDEX keys should not both be set for column `contentobject_attribute_id`

Problems with indexes of table `ezkeyword`
More than one INDEX key was created for column `keyword`

Problems with indexes of table `ezkeyword_attribute_link`
More than one INDEX key was created for column `keyword_id`

Problems with indexes of table `eznode_assignment`
More than one INDEX key was created for column `contentobject_id`

Problems with indexes of table `ezurlalias_ml`
PRIMARY and INDEX keys should not both be set for column `parent`
More than one INDEX key was created for column `parent`
More than one INDEX key was created for column `text`
More than one INDEX key was created for column `action`
More than one INDEX key was created for column `action_type`

I believe MySQL will ignore the redundant indexes, however perhaps a review of the schema would be advisable.

eZ debug

Timing:	Jan 31 2025 08:12:32
Script start
Timing:	Jan 31 2025 08:12:32
Module start 'layout'
Timing:	Jan 31 2025 08:12:32
Module start 'content'
Timing:	Jan 31 2025 08:12:32
Module end 'content'
Timing:	Jan 31 2025 08:12:32
Script end

Main resources:

Total runtime	0.0164 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	588.0156	151.1953
Module start 'layout'	0.0056	0.0028	739.2109	36.6328
Module start 'content'	0.0084	0.0064	775.8438	90.1250
Module end 'content'	0.0148	0.0015	865.9688	33.9922
Script end	0.0163		899.9609

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	15.1029	14	0.0002
Check MTime	0.0012	7.5187	14	0.0001
Mysql Total
Database connection	0.0006	3.5722	1	0.0006
Mysqli_queries	0.0038	22.9885	3	0.0013
Looping result	0.0000	0.0670	1	0.0000
Template Total	0.0012	7.1	1	0.0012
Template load	0.0009	5.6867	1	0.0009
Template processing	0.0002	1.4169	1	0.0002
Override
Cache load	0.0007	4.1707	1	0.0007
General
dbfile	0.0022	13.3743	8	0.0003
String conversion	0.0000	0.0495	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs