| Bug #12502 | Negative progress for first statement in script | ||
|---|---|---|---|
| Submitted: | 10 Aug 2005 15:32 | Modified: | 27 Sep 2005 12:46 |
| Reporter: | Anders Karlsson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
| Version: | 1.1.15 | OS: | Windows (Windows) |
| Assigned to: | Mike Lischke | CPU Architecture: | Any |
[27 Sep 2005 12:46]
Mike Lischke
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Description: The progress counter in QB is in error. In a script with just one statement, you see a negative progress of -100% while this statement is executing, fact is, you always will see a negative progress while the first statement is running (-100% if there is one statement, -50% if there are two etc). How to repeat: Open the mysql prompt the commandline and connect to database test. Open QB and connect to database test. In QB select File->New script tab. In QB in the script tab, enter the statement on one line: SELECT get_lock('foo', 60); Do NOT follow this with a CR/LF in the script (you see this as there is no linenumber 2 on the left in the script editor). Do NOT execute this statement. In mysql on the commandline, enter and execute: SELECT get_lock('foo', 60); Back in QB, click the "Execute" in the top right. QB will wait (rightfully). In the lower part of QB is the progress bar, which shows "Progress (-100%)" until the wait for the lock is over. Not a very productive SQL statement :-)