| Anonymous | Login | Signup for a new account | 02-09-10 22:08 GMT |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0008631 | phplist | Installation | public | 26-11-06 20:23 | 06-05-09 17:41 | ||||||
| Reporter | hola | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||
| Status | new | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 2.10.3 | ||||||||||
| Target Version | 2.11.X | Fixed in Version | |||||||||
| Summary | 0008631: SQL Tables creating invalid indexes | ||||||||||
| Description | Hello all, Did a fresh install of 2.10.3 and checked in phpmyadmin all the tables - below is a list of errors reported table user :: ("PRIMARY" must be the name of and only of a primary key!) table admin :: UNIQUE and INDEX keys should not both be set for column `loginname` table linktrack :: UNIQUE and INDEX keys should not both be set for column `messageid` More than one INDEX key was created for column `messageid` table linktrack_userclick :: More than one INDEX key was created for column `linkid` table listuser :: PRIMARY and INDEX keys should not both be set for column `userid` More than one INDEX key was created for column `userid` table message_attachment :: More than one INDEX key was created for column `messageid` table rssitem :: More than one INDEX key was created for column `title` table task :: UNIQUE and INDEX keys should not both be set for column `page` More than one INDEX key was created for column `page` table usermessage :: PRIMARY and INDEX keys should not both be set for column `userid` table userstats :: UNIQUE and INDEX keys should not both be set for column `unixdate` More than one INDEX key was created for column `listid` table user_attribute :: PRIMARY and INDEX keys should not both be set for column `id` table user_blacklist :: UNIQUE and INDEX keys should not both be set for column `email` table blacklist_data :: UNIQUE and INDEX keys should not both be set for column `email` More than one INDEX key was created for column `email` table message_bounce :: More than one INDEX key was created for column `user` table message_forward :: More than one INDEX key was created for column `user` table user_attributes :: PRIMARY and INDEX keys should not both be set for column `attributeid` More than one INDEX key was created for column `attributeid` More than one INDEX key was created for column `userid` | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
|
(0021412) hola (reporter) 26-11-06 22:10 |
Hello Michiel - could this issue affect performance? |
|
(0021417) michiel (administrator) 27-11-06 01:30 |
I'd have to investigate, but it's complaining about too many indexes, so that shouldn't be too much of a problem on performance. It's more the lack of indexes that would. |
|
(0050574) h2b2 (manager) 20-03-09 21:02 |
To update this report for v2.10.9, when checking the database tables with phpmyadmin I see the following warnings: admin: UNIQUE and INDEX keys should not both be set for column `loginname` attribute: PRIMARY and INDEX keys should not both be set for column `id` linktrack: UNIQUE and INDEX keys should not both be set for column `messageid` More than one INDEX key was created for column `messageid` linktrack_userclick: More than one INDEX key was created for column `linkid` listuser: PRIMARY and INDEX keys should not both be set for column `userid` More than one INDEX key was created for column `userid` message_attachment: More than one INDEX key was created for column `messageid` rssitem: More than one INDEX key was created for column `title` task: UNIQUE and INDEX keys should not both be set for column `page` More than one INDEX key was created for column `page` user: UNIQUE and INDEX keys should not both be set for column `email` usermessage: PRIMARY and INDEX keys should not both be set for column `userid` userstats: UNIQUE and INDEX keys should not both be set for column `unixdate` More than one INDEX key was created for column `listid` user_attribute: PRIMARY and INDEX keys should not both be set for column `attributeid` More than one INDEX key was created for column `attributeid` More than one INDEX key was created for column `userid` user_blacklist: UNIQUE and INDEX keys should not both be set for column `email` user_message_bounce: More than one INDEX key was created for column `user` user_message_forward: More than one INDEX key was created for column `user` Server info: phplist 2.10.9 Linux/Apache PHP 5.2.3 MySQL 4.1.12 - with database encoding set to: utf8_unicode_ci |
|
(0050638) heritage (reporter) 06-05-09 17:41 |
There seems to be still issues with index issues even on version 2.10.10 TABLE phplist_admin The following indexes appear to be equal and one of them should be removed: loginname, loginnameidx TABLE phplist_linktrack The following indexes appear to be equal and one of them should be removed: messageid, miduidurlindex TABLE phplist_task The following indexes appear to be equal and one of them should be removed: page, pageidx TABLE phplist_user_blacklist The following indexes appear to be equal and one of them should be removed: email, emailidx TABLE phplist_user_blacklist_data The following indexes appear to be equal and one of them should be removed: email, emailidx TABLE phplist_user_user The following indexes appear to be equal and one of them should be removed: email, emailidx TABLE phplist_user_user_attribute The following indexes appear to be equal and one of them should be removed: PRIMARY, userattid |
|
Notes |
