python预编译sql,在python中使用带有MySQL的预处理语句

I am trying to use SQL with prepared statements in Python. Python doesn&＃39;t have its own mechanism for this so I try to use SQL directly:

sql &＃61; "PREPARE stmt FROM &＃39; INSERT INTO {} (date, time, tag, power) VALUES (?, ?, ?, ?)&＃39;".format(self.db_scan_table)

self.cursor.execute(sql)

Then later, in the loop:

sql &＃61; "EXECUTE stmt USING \&＃39;{}\&＃39;, \&＃39;{}\&＃39;, {}, {};".format(d, t, tag, power)

self.cursor.execute(sql)

And in the loop I get:

MySQL Error [1064]: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near &＃39;&＃39;2014-12-25&＃39;, &＃39;12:31:46&＃39;, 88000000, -6.64&＃39; at line 1

What&＃39;s going on?

解决方案

Using prepared statements with MySQL in Python is explained e.g at http://zetcode.com/db/mysqlpython/ -- look within that page for Prepared statements.

In your case, that would be, e.g:

sql &＃61; (&＃39;INSERT INTO {} (date, time, tag, power) VALUES &＃39;

&＃39;(%s, %s, %s, %s)&＃39;.format(self.db_scan_table))

and later, "in the loop" as you put it:

self.cursor.execute(sql, (d, t, tag, power))

with no further string formatting -- the MySQLdb module does the prepare and execute parts on your behalf (and may cache things to avoid repeating work needlessly, etc, etc).

Do consider, depending on the nature of "the loop" you mention, that it&＃39;s possible that a single call to .execute_many (with a sequence of tuples as the second argument) could take the place of the whole loop (unless you need more processing within that loop beyond just the insertion of data into the DB).

Added: a better alternative nowadays may be to use mysql&＃39;s own Connector/Python and the explicit prepare&＃61;True option in the .cursor() factory -- see http://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlcursorprepared.html . This lets you have a specific cursor on which statements are prepared (with the "more efficient than using PREPARE and EXECUTE" binary protocol, according to that mysql.com page) and another one for statements that are better not prepared; "explicit is better than implicit" is after all one of the principles in "The Zen of Python" (import this from an interactive prompt to read all those principles). mysqldb doing things implicitly (and it seems the current open-source version doesn&＃39;t use prepared statements) can&＃39;t be as good an architecture as Connector/Python&＃39;s more explicit one.