Forums / Developer / MySQL CHECK TABLE

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

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 Exponential 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 Exponential 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.