| Bug #95059 | MySQL Workbench Hard Crashes on Migration | ||
|---|---|---|---|
| Submitted: | 18 Apr 2019 18:53 | Modified: | 29 May 2019 23:28 |
| Reporter: | Tanner Pettit | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S1 (Critical) |
| Version: | 8.0 | OS: | Windows |
| Assigned to: | CPU Architecture: | x86 | |
[18 Apr 2019 18:53]
Tanner Pettit
[18 Apr 2019 23:36]
MySQL Verification Team
Thank you for the bug report. Please provide the create table statement for a PostgreSQL table which makes possible to repeat the issue reported. Thanks.
[24 Apr 2019 14:08]
Tanner Pettit
An example of the create table statement is below.
CREATE TABLE public.copy_fact_match
(
activeid1 integer,
activeid2 integer,
active_1 character varying(30) COLLATE pg_catalog."default",
active_2 character varying(30) COLLATE pg_catalog."default",
active_3 character varying(30) COLLATE pg_catalog."default",
assists integer,
ban1 character varying(30) COLLATE pg_catalog."default",
ban10 character varying(30) COLLATE pg_catalog."default",
ban10id integer,
ban1id integer,
ban2 character varying(30) COLLATE pg_catalog."default",
ban2id integer,
ban3 character varying(30) COLLATE pg_catalog."default",
ban3id integer,
ban4 character varying(30) COLLATE pg_catalog."default",
ban4id integer,
ban5 character varying(30) COLLATE pg_catalog."default",
ban5id integer,
ban6 character varying(30) COLLATE pg_catalog."default",
ban6id integer,
ban7 character varying(30) COLLATE pg_catalog."default",
ban7id integer,
ban8 character varying(30) COLLATE pg_catalog."default",
ban8id integer,
ban9 character varying(30) COLLATE pg_catalog."default",
ban9id integer,
creeps integer,
damage integer,
damage_bot integer,
damage_done_in_hand integer,
damage_mitigated integer,
damage_structure integer,
damage_taken integer,
damage_taken_magical integer,
damage_taken_physical integer,
deaths integer,
distance_traveled integer,
first_ban_side character varying(30) COLLATE pg_catalog."default",
god character varying(30) COLLATE pg_catalog."default",
godid integer,
gold integer,
healing integer,
healing_bot integer,
healing_player_self integer,
itemid1 integer,
itemid2 integer,
itemid3 integer,
itemid4 integer,
itemid5 integer,
itemid6 integer,
item_1 character varying(27) COLLATE pg_catalog."default",
item_2 character varying(30) COLLATE pg_catalog."default",
item_3 character varying(30) COLLATE pg_catalog."default",
item_4 character varying(30) COLLATE pg_catalog."default",
item_5 character varying(30) COLLATE pg_catalog."default",
item_6 character varying(30) COLLATE pg_catalog."default",
killing_spree integer,
kills integer,
level integer,
map_game character varying(30) COLLATE pg_catalog."default",
match integer NOT NULL,
match_queue_id integer,
match_time character varying(21) COLLATE pg_catalog."default",
minutes integer,
multi_kill_max integer,
objective_assists integer,
queue character varying(30) COLLATE pg_catalog."default",
region character varying(2) COLLATE pg_catalog."default",
skin character varying(30) COLLATE pg_catalog."default",
skinid integer,
surrendered integer,
taskforce integer,
team1score integer,
team2score integer,
time_in_match_seconds integer,
wards_placed integer,
win_status character varying(4) COLLATE pg_catalog."default",
winning_taskforce integer,
playerid integer NOT NULL,
playername character varying(30) COLLATE pg_catalog."default",
ret_msg character varying(30) COLLATE pg_catalog."default",
CONSTRAINT copy_fact_match_pkey PRIMARY KEY (match, playerid)
)
WITH (
OIDS = FALSE
)
TABLESPACE pg_default;
ALTER TABLE public.copy_fact_match
OWNER to postgres;
[29 Apr 2019 23:28]
MySQL Verification Team
Thank you for the feedback. I couldn't repeat the sample table you provided: public.copy_fact_match created on PostgreSQL 11.2 and migrated by WorkBenck 8.0.16 to MySQL Server 8.0.16:
Your MySQL connection id is 17
Server version: 8.0.16 MySQL Community Server - GPL
Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> SHOW CREATE TABLE public.copy_fact_match\G
*************************** 1. row ***************************
Table: copy_fact_match
Create Table: CREATE TABLE `copy_fact_match` (
`activeid1` int(11) DEFAULT NULL,
`activeid2` int(11) DEFAULT NULL,
`active_1` varchar(30) DEFAULT NULL,
`active_2` varchar(30) DEFAULT NULL,
`active_3` varchar(30) DEFAULT NULL,
`assists` int(11) DEFAULT NULL,
`ban1` varchar(30) DEFAULT NULL,
`ban10` varchar(30) DEFAULT NULL,
`ban10id` int(11) DEFAULT NULL,
`ban1id` int(11) DEFAULT NULL,
`ban2` varchar(30) DEFAULT NULL,
`ban2id` int(11) DEFAULT NULL,
`ban3` varchar(30) DEFAULT NULL,
`ban3id` int(11) DEFAULT NULL,
`ban4` varchar(30) DEFAULT NULL,
`ban4id` int(11) DEFAULT NULL,
`ban5` varchar(30) DEFAULT NULL,
`ban5id` int(11) DEFAULT NULL,
`ban6` varchar(30) DEFAULT NULL,
`ban6id` int(11) DEFAULT NULL,
`ban7` varchar(30) DEFAULT NULL,
`ban7id` int(11) DEFAULT NULL,
`ban8` varchar(30) DEFAULT NULL,
`ban8id` int(11) DEFAULT NULL,
`ban9` varchar(30) DEFAULT NULL,
`ban9id` int(11) DEFAULT NULL,
`creeps` int(11) DEFAULT NULL,
`damage` int(11) DEFAULT NULL,
`damage_bot` int(11) DEFAULT NULL,
`damage_done_in_hand` int(11) DEFAULT NULL,
`damage_mitigated` int(11) DEFAULT NULL,
`damage_structure` int(11) DEFAULT NULL,
`damage_taken` int(11) DEFAULT NULL,
`damage_taken_magical` int(11) DEFAULT NULL,
`damage_taken_physical` int(11) DEFAULT NULL,
`deaths` int(11) DEFAULT NULL,
`distance_traveled` int(11) DEFAULT NULL,
`first_ban_side` varchar(30) DEFAULT NULL,
`god` varchar(30) DEFAULT NULL,
`godid` int(11) DEFAULT NULL,
`gold` int(11) DEFAULT NULL,
`healing` int(11) DEFAULT NULL,
`healing_bot` int(11) DEFAULT NULL,
`healing_player_self` int(11) DEFAULT NULL,
`itemid1` int(11) DEFAULT NULL,
`itemid2` int(11) DEFAULT NULL,
`itemid3` int(11) DEFAULT NULL,
`itemid4` int(11) DEFAULT NULL,
`itemid5` int(11) DEFAULT NULL,
`itemid6` int(11) DEFAULT NULL,
`item_1` varchar(27) DEFAULT NULL,
`item_2` varchar(30) DEFAULT NULL,
`item_3` varchar(30) DEFAULT NULL,
`item_4` varchar(30) DEFAULT NULL,
`item_5` varchar(30) DEFAULT NULL,
`item_6` varchar(30) DEFAULT NULL,
`killing_spree` int(11) DEFAULT NULL,
`kills` int(11) DEFAULT NULL,
`level` int(11) DEFAULT NULL,
`map_game` varchar(30) DEFAULT NULL,
`match` int(11) NOT NULL,
`match_queue_id` int(11) DEFAULT NULL,
`match_time` varchar(21) DEFAULT NULL,
`minutes` int(11) DEFAULT NULL,
`multi_kill_max` int(11) DEFAULT NULL,
`objective_assists` int(11) DEFAULT NULL,
`queue` varchar(30) DEFAULT NULL,
`region` varchar(2) DEFAULT NULL,
`skin` varchar(30) DEFAULT NULL,
`skinid` int(11) DEFAULT NULL,
`surrendered` int(11) DEFAULT NULL,
`taskforce` int(11) DEFAULT NULL,
`team1score` int(11) DEFAULT NULL,
`team2score` int(11) DEFAULT NULL,
`time_in_match_seconds` int(11) DEFAULT NULL,
`wards_placed` int(11) DEFAULT NULL,
`win_status` varchar(4) DEFAULT NULL,
`winning_taskforce` int(11) DEFAULT NULL,
`playerid` int(11) NOT NULL,
`playername` varchar(30) DEFAULT NULL,
`ret_msg` varchar(30) DEFAULT NULL,
PRIMARY KEY (`match`,`playerid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)
[30 May 2019 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".
