MySQL Bugs: #48984: Doing a SELECT or EDIT from some tables sometimes doesn't show any data

Bug #48984	Doing a SELECT or EDIT from some tables sometimes doesn't show any data
Submitted:	23 Nov 2009 10:54	Modified:	20 Aug 2010 10:05
Reporter:	Ángel Eduardo García Hernández	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.8 Beta	OS:	MacOS
Assigned to:		CPU Architecture:	Any

Description:
I had an InnoDB table with no data. Did an EDIT on it, showing no data.

I've inserted some data using our software, and re did an EDIT on the table, showing no data. Doing a SELECT * didn't show any data either, but using the "mysql" command line utility shows our data.

Other tables on the same database didn't show this behavior, although these were ARCHIVE tables, I don't know if this has any to do with this issue.

Adding more rows to the table didn't help either. The only way to show the data is to restart the software.

Anyway, after restarting the software, adding any data to this table continues to show this behavior (no data appears besides from the already appearing)

How to repeat:
The failing table continues to show this behavior. The table schema is shown in the private comments section, although this table is very basic. If any other info is needed, just ask.

Forgot to add Version and OS

Hi,

what DB version are you using and what's the DB servers OS (case sensitive filessystem)?
I tried to quickly reproduce by creating the given table on a DB ... editing works correctly here.

Sorry, forgot to add that. I know this is a very nasty bug to reproduce, because only happens in a few tables here and I don't get any pattern.

Anyway, I'm trying with a server with 20-40 databases, MySQL 5.1.39-8, Ubuntu 9.10 64 bits. Ask if you need anything else, and thank you :)

Re-reading my bug report made me think maybe I didn't express myself clearly. I mean inserting data with any other software than WB, and trying to do a SELECT in WB doesn't show up any results, but you can clearly see results with "mysql" command.

I hope this is clearer, and sorry for that :)

the connection used by a query session is launched with auto-commit off. so you have full transaction support in while query tab. in case you edit your data outside WB you need to send either a commit or a rollback to get the updated data on next execute.
please try to invoke commit/rollback either from query menu or by clicking the checkmark or cross icons in main toolbar (tooltips are missing yet for those two). after you sent a commit/rollback you should see the new data coming in upon your next execution of edit/select ...

Yes, it seems that pressing any of that buttons fix the issue. And that explains why ARCHIVE tables doesn't show this behavior. Is any "fix" expected for this? Doing only a SELECT (not an EDIT) should not raise this issue, IMHO.

Anyway, lot of thanks!

you can set the autocommit variable for your session to true yourself by sending:
set @@autocommit = 1;
to the server. we have not fully tested the effects of doing that when working with resultsets (the edit command) but for single "select sessions" it will behave the way you expected it to do.

we'll keep that open as a Feature Request for adding the ability to trigger autocommit from UI or even predefine it in connection profile.

I think since #49384 is closed, this one can be closed as well.

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/