Bug #60627 Not a bug -- result of my own improper action
Submitted: 24 Mar 2011 20:38 Modified: 24 Mar 2011 23:30
Reporter: Joshua Levin Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S5 (Performance)
Version:5.???? OS:Windows (Windows Vista)
Assigned to: CPU Architecture:Any
Tags: Programmer Error

[24 Mar 2011 20:38] Joshua Levin
Description:
I requested that MySQL WorkBench perform a query on a table that was still being updated by another program.  I should be a little bit more patient the next time.

How to repeat:
Run an action in another program, and then execute your MySQL Workbench query right afterward, without waiting for the changes to take effect.

Suggested fix:
I should put some locking mechanism in place.