Bug #633
closedduplicated lower-case table names
100%
Description
cronus4 dbemdata has lower-case nodespecdata, bindingspecdata, and launchedapplicationdata. Application exported from it has the same in some cases.
As a result, depending on the order of the application import, it causes databases outside NRAMM to have both lower and upper cased table and created problem in mysqldump because mysqldump treat the two the same.
I have not seen this on my new installations on my Mac, but might still create the lower-case table since it will still want to create the lower-case tables.
Updated by Anchi Cheng almost 14 years ago
- Status changed from Assigned to In Code Review
- Assignee changed from Anchi Cheng to Jim Pulokas
- % Done changed from 0 to 90
fixed xml files in branch at r14288, trunk at r14298 so that they won't propagate the problem further. Will need to fix cronus4 dbemdata to prevent it from happening again.
Testing after cronus4 fixes:
1. go to admin web page
2. choose Application icon
3. export an application in xml, activate "save as"
4. examining exported application xml, it should not contain the word nodespecdata or bindingspecdata
Updated by Anchi Cheng almost 14 years ago
add LaunchedApplicationData Table to leginonDBSchema.xml to prevent launchedapplicationdata from creating. Also make sure it does not export.
r14289 in trunk, r14299
Testing:
1. go to admin web page
2. choose Application icon
3. export an application in xml, activate "save as"
4. examining exported application xml, it should not contain the word "launchedapplicationdata" or "LaunchedApplicationData"
Updated by Jim Pulokas almost 14 years ago
- Status changed from In Code Review to In Test
- Assignee changed from Jim Pulokas to Anchi Cheng
looks good. and if we rememeber in the future, we can remove the lowercase name from leginon.inc once our database is cleaned up.
Updated by Anchi Cheng almost 14 years ago
- Assignee changed from Anchi Cheng to Eric Hou
- % Done changed from 90 to 100
removed the lower-cased tables at cronus4. import/export tested fine.
Eric, could you test leginonDBSchema.xml by starting myamiweb/setup on an empty database?
Updated by Eric Hou almost 14 years ago
- Status changed from In Test to Closed
Just test on brand new installation.
All there tables got created in leginondb database as follow.
BindingSpecData
NodeSpecData
LaunchedApplicationData
Thanks.
Eric
Updated by Amber Herold almost 14 years ago
- Target version changed from 8 to Appion/Leginon 2.0.0
- Affected Version set to Pre-2.0