MySQL Bugs: #113231: Error parsing DLL When modifying table with the row setting: DEFAULT uuid()

Bug #113231	Error parsing DLL When modifying table with the row setting: DEFAULT uuid()
Submitted:	27 Nov 2023 10:10	Modified:	27 Nov 2023 11:31
Reporter:	Igor Zukina	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	8.0.34	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Maria DB, I configured the ROW to generate UUID on insert. The Database is working correctly, creating the UUID.
However, the workbench does not allow putting uuid() function into the default statement. It reverts it to 'uuid()' string.
When I alter the table column using the SQL script and then try to use a workbench to modify the table, it crashes with dll parsing error.

Viewing the 'dll' reports the error in "CREATE TABLE"  line:

device_UUID` char(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL DEFAULT uuid()

having a 'x' and underlining as error the "uuid()".

How to repeat:
ALTER TABLE your_table
CHANGE device_UUID 
device_UUID char(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL DEFAULT (UUID())

Suggested fix:
The workbench appears to have no uuid() function registered, so it is not recognised as a valid function. (my guess and hard to believe) but it could be anything else.

Hello Igor Zukina,

Thank you for the bug report.
Imho this is duplicate of Bug #105169, please see Bug #105169.
Also, note that server MariaDB isn't supported by MySQL Workbench. Thanks.

Regards,
Ashwini Patil