Bug #68692 | Workbench model synchronization timeout too short/non-configurable | ||
---|---|---|---|
Submitted: | 16 Mar 2013 16:35 | Modified: | 21 Jul 2013 13:44 |
Reporter: | James R | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
Version: | 5.2.47 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | model, synchronize, timeout, workbench |
[16 Mar 2013 16:35]
James R
[4 Apr 2013 14:42]
Armando Lopez Valencia
Thanks a lot for your report.
[4 Apr 2013 15:42]
James R
By the way though, due to the fact that you can't use Workbench for anything else while a query is running if you do it through the wizard, you are far better off on long queries copying the generated SQL and pasting it into a standard query tab. When done this way, you can continue to use the rest of the program, including running other queries in separate connections. Given this, while it would be nice to not wait 10 minutes and then find out the query is going to fail, I can't recommend using the wizard for long queries anyway. Perhaps the easiest and most effective fix here is just a notice that this will happen so that users know to work around it.
[21 Jun 2013 5:15]
Alfredo Kojima
If you have that many rows in a standards inserts tab for a table in modeling, there's probably something wrong with your modeling. Standard inserts are not meant to contain table dumps, it's just for initializing pre-defined constant data.
[21 Jun 2013 13:44]
Alfredo Kojima
Hi, please provide detailed instructions about how to repeat. Your report doesn't make much sense, as it is filed under administration, but it seems to be about Modeling. You mention synchronization, but Inserts data isn't included in Synchronization. Thanks.
[22 Jul 2013 1:00]
Bugs System
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".
[2 Jul 2021 19:00]
Michael Krueger
This is still an issue in MySQL Workbench 8.0.25 build 788958 CE (64 bits), exactly as described above: any synchronization actions performed in the Synchronize Model with Database wizard will time out after exactly 30 seconds, regardless of any of the timeout settings in Workbench Preferences. I believe Alfredo Kojima misunderstood James R’s description of the problem: the issue is not with using the Synchronize Model with Database wizard to create large tables, but rather with using it to update the schema of an existing database that already contains large tables. Steps to reproduce: 1. Create or choose a database that contains one or more large (say, 20,000 rows or more) tables. 2. Open the schema of the database in MySQL Workbench and add a column to one of the large tables. 3. Attempt to use the Synchronize Model with Database wizard to synchronize this schema update to the database. Expected result: Provided that the timeout values in Workbench Preferences: SQL Editor: MySQL Session are set high enough, the operation completes successfully Observed result: The operation times out after exactly 30 seconds, regardless of the timeout values in Workbench Preferences: SQL Editor: MySQL Session.