m4v3rick unfortunately, I don't have any computer with MariaDB to troubleshoot.
At this point it's still unclear if it's MariaDB related. If someone finds a way to reproduce the error on a regular MySQL install I can take a quick look on my side. Otherwise this will take at least half an hour to troubleshoot and I don't have time for that unless someone sponsors it.
I looked at the Laravel issue tracker last time and couldn't find anything. If someone described this problem elsewhere online it's also possible we find a way to modify the code that I can try even if I can't test on MariaDB. But at this point I have absolutely no idea what would need changing.
To me it still looks like a potential issue with the Laravel method itself. Maybe a patch has already been released in a later Laravel version which would explain why there are no reports for this elsewhere online, but it's very hard to tell for sure.
