DanielLeens commented on issue #10451: URL: https://github.com/apache/seatunnel/issues/10451#issuecomment-6145196225
Thanks for tracing this all the way to the derived `UNSIGNED` flag. I checked the current open work and agree that #12333 is the root-cause fix for this issue: a SET value name containing `UNSIGNED` must not make the column itself unsigned. #12742 is the related guard/test cleanup. Please do not add a standalone `SET UNSIGNED` production mapping as the resolution for this report. That would preserve an invented type instead of preventing it. The restricted `database-pattern` remains a valid workaround for affected released deployments, while this issue should stay open until the root fix is merged and its relevant validation has completed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
