Project

General

Profile

Actions
Copy link

Bug #564

closed

strange database indices

Added by Anchi Cheng over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Anchi Cheng
Category:
-
Target version:
-
Start date:
05/25/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
Show in known bugs:
Workaround:

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?

Related issues 1 (0 open — 1 closed)

Related to Appion - Bug #565: schema13713.py renames apParticleData to apparticledataClosedEric Hou05/25/2010

Actions
Actions
Copy link
 #1

Updated by Neil Voss over 14 years ago

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

Actions
Copy link
 #2

Updated by Anchi Cheng over 14 years ago

ap5 apParticleData

Actions
Copy link
 #3

Updated by Anchi Cheng over 14 years ago

  • Assignee changed from Anchi Cheng to Neil Voss
Actions
Copy link
 #4

Updated by Neil Voss over 14 years ago

This appears to be a chronic problem with the ApParticleData table? Same thing in ap6.

Actions
Copy link
 #5

Updated by Neil Voss over 14 years ago

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?

Actions
Copy link
 #6

Updated by Neil Voss over 14 years ago

  • Assignee changed from Neil Voss to Anchi Cheng

Anchi, does this occur on Scott's tables too?

Actions
Copy link
 #7

Updated by Anchi Cheng over 14 years ago

  • Assignee changed from Anchi Cheng to Neil Voss

No.

Actions
Copy link
 #8

Updated by Neil Voss over 14 years ago

  • 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?

Actions
Copy link
 #9

Updated by Eric Hou over 14 years ago

  • 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

Actions
Copy link

Also available in: Atom PDF