Bug #565
closed
schema13713.py renames apParticleData to apparticledata
Added by Anchi Cheng over 14 years ago.
Updated over 14 years ago.
Affected Version:
Appion/Leginon 2.0.1
Description
Saw that in Scott's database. It does not seem to affect it, but is very strange.
probably relates to bug #566. Even though that is fixed, label column does not yet exist when it is indexed.
- Status changed from Assigned to New
- Assignee deleted (
Neil Voss)
I have no clue why this happens and have no ideas to fix it.
- Status changed from New to Closed
I tried on Suse 11.2, and it does not happening after I ran the upgrade scrips.
Case close.
Eric
- Status changed from Closed to In Code Review
- Assignee set to Neil Voss
- % Done changed from 0 to 100
Finally found why. CREATE INDEX caused the table name to change to all lower case, at least on my computer (MySQL 5.0.67). I was able to reproduce the error. It could be that it's mapping to ALTER TABLE is not exact. It turns out that apParticleData was the only table in schema-r13713.py needed to go through the query, and therefore the only one affected. committed as r14260 in the trunk. r14261 in the branch
- Status changed from In Code Review to In Test
- Assignee changed from Neil Voss to Anchi Cheng
Good find, this is probably related to the multi-index DEF_timestamp thing too. This is hard to test, has Eric tested?
- Assignee changed from Anchi Cheng to Eric Hou
Eric was not able to reproduce the error on his computer before. I tested on mine after my change on my computer. Maybe Eric wants to try again?
I will test this one today.
Thanks.
I Just tested on Scott database and all the tables look good.
Thanks.
- Status changed from In Test to Closed
- Affected Version set to Appion/Leginon 2.0.1
Also available in: Atom
PDF