Comments - CAST
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
I just recently noticed on my development db (windows based MariaDB) a stored procedure using cast worked and exported casting as varchar(255) while production db (ubuntu based MariaDB) thrown an error for having a syntax error and needed a change from varchar(255 to char... After changing just that everything else worked fine... also I have an IN variable also defined as varchar(255) but MariaDB did not complain about that.
Can you create a ticket on JIRA? Doesn't sound like that should be happening.