Bug #16785 No argument found for format '%`
Submitted: 25 Jan 2006 15:51 Modified: 1 Dec 2006 14:27
Reporter: Aaron Freeman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1x OS:Windows (Windows 2000 & XP)
Assigned to: Mike Lischke CPU Architecture:Any
Tags: Source Editors

[25 Jan 2006 15:51] Aaron Freeman
Description:
I can never edit a view in query browser.  All the views that I create are from right clicking the table/sp/view inventory list and clicking "Create New View".  After it has been created and I log back in (or close out the tab), if I try to edit, I get an error in the status bar that says:

"No argument for format '%`"

If I copy the SQL of the view in my clipboard it reads:

"DROP VIEW IF EXISTS `darkwind`.`vw_slotgames`;
CREATE ALGORITHM=UNDEFINED DEFINER=`gameserver`@`%` SQL SECURITY DEFINER VIEW  `darkwind`.`vw_slotgames` AS select `slotgames`.`player` AS `player`,count(0) AS `total`,(count(0) * 10) AS `APPaid` from `slotgames` group by `slotgames`.`player` order by count(0);"

However, this is not what I wrote in the beginning when I created the view.  I assume this is the SQL browser manipulating it to fit with the database.

How to repeat:
See description.

Suggested fix:
The problem obviously lies with the:

"CREATE ALGORITHM=UNDEFINED DEFINER=`gameserver`@`%` SQL SECURITY"

Which is all generated AFTER I store the view in the database.
[26 Jan 2006 23:13] Jorge del Conde
Thanks for your bug report.  I was able to consistently reproduce this bug.
[12 Feb 2006 10:44] Valeriy Kravchuk
Bug #17330 is marked as a duplicate of this one.
[12 Sep 2006 17:09] Dan Kloke
a similar issue occurs when editing stored procedures/functions. the error message  makes reference to a syntax error near "$$ 

DELIMITER".

the workaround described at Bug #17330 works.  I just remove the DEFINER=`someuser`@`%` portion and can run the script to create the view or stored proc/func.
[1 Dec 2006 14:27] Mike Lischke
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/