Actions
Bug #3521
closedcommitSubStack function gives mysql syntax error due to using direct mysql insert
Start date:
09/01/2015
Due date:
% Done:
0%
Estimated time:
Affected Version:
Appion/Leginon 3.2
Show in known bugs:
No
Workaround:
Description
got an error similar to this
File "/home/acheng/myami/appion/appionlib/apStack.py", line 555, in commitSubStack
sinedon.directq.complexMysqlQuery('appiondata',sqlcmd)
File "/home/acheng/myami/sinedon/directq.py", line 24, in complexMysqlQuery
results = cur.selectall(query)
File "/home/acheng/myami/sinedon/sqldb.py", line 42, in selectall
self.c.execute(strSQL, param)
File "/usr/lib64/python2.6/site-packages/MySQLdb/cursors.py", line 173, in execute
self.errorhandler(self, exc, value)
File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
raise errorclass, errorvalue
_mysql_exceptions.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'guppy-18', 49153), 50), dbid: 10, referent: weak]','DataReference[class: ApStack' at line 1")
Updated by Anchi Cheng about 9 years ago
- Related to Support #3355: substack direct queries added
Updated by Anchi Cheng about 9 years ago
- Assignee changed from Anchi Cheng to Gabriel Lander
r19115 fixes this particular case and add a general tool to get the proper column name from an sinedondata instance.
Gabe, you can use the function I added in directq to correct the other ones. I think you have quite a few of these.
Updated by Gabriel Lander about 9 years ago
- Status changed from Assigned to Closed
This is great, Anchi, I'll definitely integrate this function into the direct queries.
Actions