#3067 (ok 3.3.6) Issuing truncate queries cause problems
If I issue truncate queries like:
TRUNCATE `cms_page_property_tmp`;
TRUNCATE `cms_tmp`;
TRUNCATE `sitemap_tmp`;
TRUNCATE `suche_tmp`;
and submit them using the SQL-textarea:
1. I'm not asked like I would on delete queries
2. the output is broken on the next page twice:
- the repeated SQL query in the contains mysql-responses which are html escaped twice ( is readable there for the user)
- the preinserted SQL-command in the SQL-textarea contains the mysql-responses, too (so one cannot issue this query again w/o editing it):
TRUNCATE `cms_page_property_tmp`;# MySQL lieferte ein leeres Resultat zurück (d. h. null Zeilen).
TRUNCATE `cms_tmp`;# MySQL lieferte ein leeres Resultat zurück (d. h. null Zeilen).
TRUNCATE `sitemap_tmp`;# MySQL lieferte ein leeres Resultat zurück (d. h. null Zeilen).
TRUNCATE `suche_tmp`;# MySQL lieferte ein leeres Resultat zurück (d. h. null Zeilen).
Discussion
About 1, you're right and this is fixed for 3.3.6.
About 2, I changed this part of the message to (d.h. null Zeilen), please tell me if it's ok.
However, the MySQL responses are prefixed with a # sign which introduces them as comments so they can be resubmitted (result is not pretty but it works).
# isn't a SQL-comment!?
Yes, in MySQL.
http://dev.mysql.com/doc/refman/5.1/en/comments.html