Bug #76091 Sybase ASE migration fails to detect many field data types
| Submitted: | 2 Mar 2015 10:00 | Modified: | 4 Mar 2015 8:15 |
|---|---|---|---|
| Reporter: | Chris Keene | Email Updates: | |
| Status: | Won't Fix | Impact on me: | |
| Category: | MySQL Workbench: Migration | Severity: | S3 (Non-critical) |
| Version: | Workbench 6.2, 8.0 | OS: | Windows (Windows 7) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | sybase | ||
[2 Mar 2015 10:00]
Chris Keene
[4 Mar 2015 8:15]
Mike Lischke
Thanks for filing the bug report. Sybase ASE support is still under development in MySQL Workbench, but should work for many situations already. However, we need to investigate your specific case to find a solution.
[21 May 2020 12:14]
MySQL Verification Team
Bug #99193 marked as duplicate of this one.
[14 Sep 18:02]
Omer Barnir
Posted by developer: This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained. MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation. Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.055 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.