Actions
Bug #1956
openone-to-one relationship for ApSelectionRun DEF_id to its rundir
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/27/2012
Due date:
% Done:
0%
Estimated time:
Affected Version:
Appion/Leginon 2.2.0 (trunk)
Show in known bugs:
No
Workaround:
Description
Liz got a sinedon error that ends with
File "/usr/lib/python2.4/site-packages/MySQLdb/connections.py", line 35, in defaulterrorhandler
raise errorclass, errorvalue
_mysql_exceptions.IntegrityError: (1062, "Duplicate entry '6813' for key 2")
It turns out that earlier appion database imposes a unique flag on apSelectionData.`REF|ApPath|path`. Gabe's helical stuff wants to add a new selection run in the same path even as kind of subrun. Shall we remove uniqueness constraint? Does anyone use that property in their code , i.e., assumes one-to-one relationship of selectionrun and the rundir? I think the most likely place that this is required is in the workflow where a run needs to be repeated but the subrun in this case can not berepeated in one step, anyway.
I will remove the constraint in the appion database Liz works on (ap90) so that she can move on but can change that back later.
Actions