Anyone tried C# 10 with Aspire 13 + EF 13 + MySQL?

Inserting NULL into a column that has been declared NOT NULL. For multiple-row INSERT statements or INSERT INTO ... SELECT statements, the column is set to the implicit default value for the column data type. This is 0 for numeric types, the empty string ('') for string types, and the “zero” value for date and time types. INSERT INTO ... SELECT statements are handled the same way as multiple-row inserts because the server does not examine the result set from the SELECT to see whether it returns a single row. (For a single-row INSERT, no warning occurs when NULL is inserted into a NOT NULL column. Instead, the statement fails with an error.) Setting a numeric column to a value that lies outside the column range. The value is clipped to the closest endpoint of the range. Assigning a value such as '10.34 a' to a numeric column. The trailing nonnumeric text is stripped off and the remaining numeric part is inserted. If the string value has no leading numeric part, the column is set to 0. Inserting a string into a string column (CHAR, VARCHAR, TEXT, or BLOB) that exceeds the column maximum length. The value is truncated to the column maximum length. Inserting a value into a date or time column that is illegal for the data type. The column is set to the appropriate zero value for the type. https://mariadb.com/kb/en/start-transaction/#ddl-statements DDL statements cannot be run in transactions; they will automatically commit the in-progress transaction and start a new one. Reversing a schema change requires explicitly doing so, or restoring from backup.