slightly off topic. I'm confronted with the possibility that Perl code of mine is corrupting a MariaDB sever.

I wrote some SQL which recursively descends into a nested tree in a table with id - parent-id relations. Turned out that my test instance of MariaDB was far newer than the one in production (Version 10.0.x about 4 years old).

Hence I couldn't use a BEGIN NOT ATOMIC clause, to keep the recursion inside a single transaction.

So I fell back to the possibility to dynamically create a stored procedure and execute it when needed.

This worked pretty fine, now one of our production servers can't use SPs anymore

Cannot load from mysql.proc. The table is probably corrupted

Question: Is it officially discouraged to dynamically drop, create and execute SPs from Perl? Are there dangerous race conditions?

I suppose that a version upgrade would solve the issue and hopefully we won't need to roll back to saved state.

In the end I can only politely remind the DBA to keep the MariaDB Versions in sync.