MySQL Bugs: #103026: sequence item 6: expected str instance, bytes found

Bug #103026	sequence item 6: expected str instance, bytes found
Submitted:	18 Mar 2021 2:32	Modified:	2 Apr 2021 18:50
Reporter:	Raj Padnani	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	8.0.23, 8.0.25, 8.0.26, 8.0.33	OS:	Windows (Microsoft Windows 10 Home)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\Raj Padnani\AppData\Roaming\MySQL\Workbench\log\wb.log]

After upgrading to 8.0.23 (from 8.0.18)

When choosing File->Run SQL Script from WorkBench Menu, I get this error:

sequence item 6: expected str instance, bytes found

How to repeat:
Choose File->Run SQL Script from workbench Menu

Also, After selecing the file from File->Run, I choose a Default Schema name, and if I choose Default Character Set to utf8mb4, the WB just crashes and exits!!

wb.log

Attachment: wb.log (application/octet-stream, text), 9.80 KiB.

wb log file

Attachment: wb.1.log (application/octet-stream, text), 9.64 KiB.

If I try to install an older version of WB, 8.0.20, the installer errors out stating a newer version is already installed. How can I circumvent this and install an older version of MySQL WB CE?

Thanks.

Hello,

Is there any update on this? Any help, pointers you can provide?

Thanks.

Hello Raj Padnani,

Thank you for the bug report.
Verified as described.

Regards,
Ashwini Patil

8.0.23 test results

Attachment: 103026_test_results.png (image/png, text), 45.44 KiB.

Bug #103053 marked as duplicate of this one.

I am having the exact same error come up using this version of the workbench.

Hello Ashwini,

This issue is really troubling me - CAN YOU PLEASE PROVIDE A RESOLUTION!!!!!!!!!!

Once again, to reiterate, Every time I do File -> Run SQL Script I get error similar to below:

Preparing...
Importing t2.sql...
Finished executing script
mysql: [ERROR] Failed to open required defaults file: c:\users\raj
mysql: [ERROR] Fatal error in defaults handling. Program aborted!
Operation failed with exitcode 1

Hello,

Can you please provide a resolution on this issue? 

Thanks,
Raj

You can try use MySQL command line client. I had the same problem.

My solve is use this command line client. There is I choose my schema and insert:

source C:\folder\with\dump\file.sql

Good day, Raj!

I have the same problem with 8.0.25. Any solutions?

Bug #104064 marked as duplicate of this one.

Same issue for me. It is a blocking bug: I am unable to load large file in local.

If you are trying to load data (e.g. output from mysqldump), have you tried Data Import under Administration?

If you choose Import for Self-Contained File and click Start Import does it provide the desired results?

If you are trying to load data (e.g. output from mysqldump), have you tried Data Import under Administration?

That did work for me. Thanks.

Bug #104383 marked as duplicate of this one.

Error: mysql sequence item 6: expected str instance, bytes found

Attachment: Error item6.png (image/png, text), 62.78 KiB.

I tried the same operation as "[30 Jun 20:25] Charles Blake"
It works for me too.

issue still occurs for us in version 8.0.27

Is this fixed? Any news? Still happening in 8.0.26

I created an account just to make this post.
Please fix this bug, it has been triggering me for a year or something now.

I'm sick of using the MySQL CLI to load dumps/large files instead of this convenient File -> Run SQL Script option in Workbench. This used to work for me just fine, what changed?

Also please add a dark mode built in theme. I understand the stance of the Workbench team thus far has been to let the OS decide the color scheme, but this doesn't work for dark mode on Windows for some reason...

8.0.28 same error while importing a sql file via Run SQL Script...

One a side note, I honestly haven't used a buggier app than this one.  Someone needs to advocate for better testing.

I get the same error, then looking at script I see it has a commentary /*!40101 SET NAMES utf8mb4 */;  then I create the  schema with utf8mb4 as character set  and default as collating sequence y it work fine.

I've encountered this issue when trying to create a new schema on a Db from a saved sql file - rather than going through the whole migration interface repeatedly (testing environment). 

What worked for me is to copy the contents of the sql file, paste into a new sql query tab within MySQL Workbench, then execute. Hope this helps anyone else.

I have started facing the same issue recently while importing the SQL file into the schema. I am using workbench version 8.0.28
Is this issue with some specific Workbench? Can someone please help how to fix it as I need to import 10 GB file which cannot be possible to workbench editor.

This has been an ongoing problem for us for over a year.

It's difficult for me to understand why after nearly two years this bug isn't fixed. I guess you guys don't really care about community versions.

Issue still persists, tried also to make a mysqldump on the remote server, then transfer the SQL file, then import it, but it doesn't work neither with "Run SQL script" nor with Data import. 

I found a partial workaround though, run the export with the first option, "each table in a separate file", then import and it will work for all the tables except the one with the problem

Bug #110772 marked as duplicate of this one.

Greetings all,
    I have the same issue while trying to run a SQL script from the MySQL Workbench (8.0.33). 

Would be glad if someone could help me!

Kind Regards,
Kausik D

This issue appears to be present in Workbench 8.0.34 also. Downgrading to 8.0.22 resolves the issue.

Just wanted to add that the solution for myself was to downgrade it to 8.0.22 like said before. Bummer that I lost hours on this bug

This bug is marked critical and is still open after 3 years?!!!

select actor_id, frist_name as nombre, last_name as apellido, last_update from sakila.actor;

Attachment: sakila-data.sql (application/octet-stream, text), 3.20 MiB.

Oracle has left this bug report sitting here for 3 YEARS ????

2025 and the problem is still active