Devart Forums

Hi,

We've just started using dbForge Studio for mySql and have come across and major problem which may affect our usage of the product in the future.

BACKGROUND:
I have a database with a table called 't_log' which simply logs messages from an application. The application only INSERTs to the table, it never reads from it in any way, shape or form. Everything is running on Windows and the application is a web app hosted in IIS7 and uses the .Net Connector to access the database.

PROBLEM:
When I access the table in dbForge Studio (either by right click on table->Retrieve Data or new SQL->SELECT * FROM t_log;),even though it is read-only and cached updates are switched on, the application 'hangs' while dbForge has the results open. The applicaton will eventually time out and throw an exception. If I close the dbForge results view while the application is 'hung' it instantly frees up and continues working. The application behaves as if there is a lock on the table, but no locks are reported anywhere.

Can anybody help with this issue, or explain what is happening?

I really like dbForge Studio and it would be a real shame to have to stop using it.

(BTW - I CANNOT reproduce this problem in mySQL Workbench or Toad for mySql)

EDIT: dbForge Studio for mySql Professional Edition Version: 6.0.189 - Registered User

Thanks in advance.
Dave

We are currently investigating this issue and will answer you as soon as possible.

When viewing table data in fetching mode (Paginal mode is turned off), dbForge Studio for MySQL doesn't receive all data at once, but gradually upon request (for instance: when scrolling data in the grid). When using this mode, there is not closed cursor pending and, as a result, MyISAM tables are locked for editing unlike InnoDB tables.

In such situation you should navigate to the last record of the retrieved data in Data Editor in order to finish fetching table data (the pending cursor will be closed) or use Paginal mode.

To switch paginal mode on, press the 'Paginal Mode' button on the toolbar of Data Editor and set 'Page Rows Count'.

If you would like paginal mode to be turned on by default, please follow the procedure:

1. Select 'Tools -> Options' from the main menu. The 'Options' window opens.
2. Navigate to the 'Data Editor -> General' branch.
3. Select the 'Use paginal mode by default' option and set 'Initial page size'.

Also, we noticed that you are using an old build of dbForge Studio for MySQL. Please note that there is a newer build 6.0.265 available for downloading: http://www.devart.com/dbforge/mysql/stu ... nload.html

That makes so much sense! I tried your suggestion and it worked 100%.

Thank you so much for your help!!

Please let us know if other questions arise.

Thanks for this. It answers my problem with locked records.

Bump after 7 years. Still an issue.
Stopped production across 3 manufacturing sites for an hour. Luckily, no one was hanged.

Suggestion: Instead of "Warning, this table is in read-only mode" I'd rather see "Warning, this table is locked and is inaccessible for other requests".
Much more important, IMHO.

We will investigate it when developing the next product versions.