Bug #118091 Issue with Auto-Generated SQL for Tables Containing BIT(1) Columns

• Submitted: 30 Apr 2:30
• Modified: 30 Apr 11:18
• Reporter: Harry Zhang
• Status: Duplicate
• Category: MySQL Workbench
• Severity: S2 (Serious)
• Version: 8.0.42
• OS: MacOS
• CPU Architecture: ARM

[30 Apr 2:30] Harry Zhang

Description:
Dear [Recipient's Name],

I hope this message finds you well.

I would like to report a potential issue related to how SQL statements are auto-generated when working with tables that contain multiple BIT(1) columns.

This behavior could potentially lead to incorrect queries or unexpected results.

Please let me know if any additional details are needed.

Best Regards,
Harry

How to repeat:
Steps to Reproduce:

Create a table that includes more than one BIT(1) column, followed by columns of other data types.

Execute a query:

SELECT * FROM the_table_with_bit;  

Edit the result by inserting new rows or updating existing ones on GUI result table.

Click on the Apply button to generate the corresponding SQL statements.

Observed Behavior:

The auto-generated SQL may omit the leading b for BIT values.

In some cases, the generated SQL applies the leading b prefix to all values, including those not of BIT type.

[30 Apr 11:18] MySQL Verification Team

Hello Harry Zhang,

Thank you for the bug report.
Imho this is duplicate of Bug #79604, please see Bug #79604.

Regards,
Ashwini Patil