Bug #17471 MTK does not migrate sequences
| Submitted: | 16 Feb 2006 15:20 | Modified: | 19 May 2009 12:53 |
|---|---|---|---|
| Reporter: | Kristian Koehntopp | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Migration Toolkit | Severity: | S4 (Feature request) |
| Version: | 1.0.23 | OS: | Windows (Windows) |
| Assigned to: | CPU Architecture: | Any |
[19 May 2009 12:53]
Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Migration Tool into MySQL Workbench. We won't add this feature request anymore. More informations about MySQL Workbench you will find here: http://dev.mysql.com/workbench/
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.048 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.
Description: Currently, MTK has no method to migrate sequences. How to repeat: Create an Oracle schema def with a sequence. Migrate it. Watch the sequence not being migrated. Suggested fix: Create standard stored functions curval() and nextval(), create a table _seq. Create the sequence "seqname" as create view seqname as select nextval("seqname") as nextval; This will allow the use of seqname.nextval as in oracle. It does not handle seqname.curval transparently, but that can easily be emulated by "select curval('seqname') as curval".