By westsyde on

I am using Panels 5.x-2.0-rc1a and Views 5.x-1.6

I have the following issues to resolve.

Problems with indexes of table `panels_mini`
The following indexes appear to be equal and one of them should be removed: name, name_2
Problems with indexes of table `view_view`
The following indexes appear to be equal and one of them should be removed: name, name_2

I have read the forum however there appears to be no clear procedure to resolve this issue, as apparently this module related issue was meant to have been resolved some time ago.

Do I simply delete the two table rows in question or is the procedure more involved than that?

Thanks

⋅ Categories: Drupal 5.x

Comments

pobster’s picture

pobster commented

The issue is with table indexing not with the rows themselves, if you wish (as indexing is only really to allow faster data sorting - you're kind of specifying those fields will be used for sorting more often than the others?) remove the indexing - just don't remove the table rows themselves! Panels fails schema and coder tests, not sure why no-one is bothered about it...

Pobster

westsyde’s picture

westsyde commented

I take that means that the name_2 keyname/index is not considered a database row and that it should be removed.
Others than deleteing the name_2 key keyname/index I can not see any other way to remove the index.

Is that right?

pobster’s picture

pobster commented

Well... Yeah... But you really need to understand what these are and why they're not technically important? This is why you can delete them - BUT they're NOT rows, they're keys/ indexes and do not hold data themselves - they're present to let mysql know that a particular column or combination of columns will be used often and as such, will need 'indexing' like for instance, how Drupal indexes your pages for searching. It's caching if you understand that concept?

Pobster

westsyde’s picture

westsyde commented

Thanks for the info. It’s much appreciated. That clarifies what I imagined they were for.

I now know that the key/indexes are not rows but more like content of a row/s related to (in this case) search indexing.

If common sense prevails, I would say that these particular pages will be used often, but the content itself will not change more than about twice a year, so the primary and unique indexes should be more than satisfactory.

MartinDeJong’s picture

MartinDeJong commented

I noticed almost each column is indexed in Drupal. Im general, indexes slow down updates and inserts. They can increase retrieval speed when they are used in the predicate (WHERE-clause) but only then when the number of different values is high.
You can imagine that which a field like Gender that using an index is useless, since for each record it needs to reads, one (or even more) fro the index and one for the actual record.