MySQL Bugs: #76765: MySQL workbench not showing correct query data

Bug #76765	MySQL workbench not showing correct query data
Submitted:	21 Apr 2015 7:43	Modified:	22 May 2015 10:04
Reporter:	DAWOOD CUTLERYWALA	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.2.5	OS:	Windows (Microsoft Windows 7 Ultimate Service Pack 1)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
When I query a table either by writing a query or using the select rows option for the first time after starting MySQL workbench, I get the right data. Every time I rerun the query I do not get the refreshed results. When this happens, I tried querying other tables (running the query for first time) I get the right results only for the first time. When I rerun the query, the data is not refreshed. I tried closing the query tab and opening a new tab, but that too does not help. I have to close the connection and reopen the connection in order to see the correct results.

How to repeat:
1. Start MySQL Workbench 
2. Make a connection to either a local or remote database
3. Right click a table and click Select Rows
4. This opens a new query tab and shows the select * results for that table
5. Now re-run the query, either by clicking on any of the execute query option OR click on the refresh button above the results grid.
6. The query tab shows you the same results as before although the data in the database has changed.
7. Now close the connection tab and make a new connection to the same database as selected in 1.
8. Right click the same table as in 2 and click Select Rows
9. This opens a new query tab, showing you the correct results.

Suggested fix:
The workbench should refresh data when he query is re-run using any of the re-run options.

Thank you for the bug report. After ran the query how you changed the table data? I did using the command client and the refresh button shows the news rows inserted, so I can't repeat as described. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".