Bug #40648 Inbound syncronization does nothing
| Submitted: | 11 Nov 2008 19:28 | Modified: | 8 Feb 2010 14:57 |
|---|---|---|---|
| Reporter: | Kevin Peno | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 5.0.26 | OS: | Windows (Vista 64bit) |
| Assigned to: | Alexander Musienko | CPU Architecture: | Any |
| Tags: | CHECKED, syncronization, workbench | ||
[11 Nov 2008 19:28]
Kevin Peno
[13 Nov 2008 17:41]
MySQL Verification Team
Thank you for the bug report.
[7 Apr 2009 1:24]
Eli Garcia
Just to chip in, this issue is causing me a lot of hassle too. I may work alter a database from outside workbench, and then find that I have to reverse engineer the whole thing in order to update a simple field change or something.
[8 Feb 2010 11:44]
Johannes Taxacher
fixed in repository for 5.1
[8 Feb 2010 14:57]
Tony Bedford
An entry has been added to the 5.1.19 changelog: When synchronizing with a live database, if the direction of synchronization was changed to inbound, then the script generated indicated that no inbound changes would be made.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.