Bug #564
closed
Added by Anchi Cheng over 14 years ago.
Updated over 14 years ago.
Description
I notice some strange index naming when looking at phpMyAdmin. Don't know if it is meant that way.
apParticleData: label_index8
Also, ap5 has three indices for DEF_timestamp. Did these got there by doing the upgrade?
- Subject changed from strang database indices to strange database indices
- Status changed from New to Assigned
- Assignee changed from Eric Hou to Anchi Cheng
TEXT fields cannot be indexed unless you specify the number of characters to index, in this case we are indexing the first 8 characters, hence the name `label_index8`. This is another reason VARCHAR(8) would be a better choice.
The program checks for existing indexes and does not perform an index if one exist. Anchi can you point me to the Table with the multiple indexes for DEF_timestamp.
- Assignee changed from Anchi Cheng to Neil Voss
This appears to be a chronic problem with the ApParticleData table? Same thing in ap6.
This happened on all the databases? I still have no clue how. To remove:
SHOW INDEX FROM `ApParticleData` WHERE Column_name='DEF_timestamp';
ALTER TABLE `ApParticleData` DROP INDEX `DEF_timestamp_2`;
ALTER TABLE `ApParticleData` DROP INDEX `DEF_timestamp_3`;
Anchi, does this occur on Scott's tables too?
- Assignee changed from Neil Voss to Anchi Cheng
Anchi, does this occur on Scott's tables too?
- Assignee changed from Anchi Cheng to Neil Voss
- Status changed from Assigned to In Test
- Assignee changed from Neil Voss to Anchi Cheng
I think your fix for Bug #565 fixes this, any idea how to test?
- Status changed from In Test to Closed
I just tested it again by created a new project and assign a new ap database. It did not create extra index for ApParticleData.
But I found out there are lots of our current ap databases have this problem.
Thanks.
Eric
Also available in: Atom
PDF