The Ultimate Guide to High Availability with MariaDB

Comments - Storage engine support and compatibility constraints

8 years ago Dba Btissam
Re: Storage engine support and compatibility constraints

Thanks for your reply.

-You said "There is a certain API that plugins should use": could you give a link where those APIs are listed for a given plugin please (engines , UDFs..) this in order to check the compatibility manually if necessary?

-In instance, If we developp a process under MariaDb server 10.1 using stored proc+functions, tables from different supported engines (say CONNECT, SPIDER...),UDFs...and then MariaDb is upgraded to a newest version which doesn't support CONNECT or a specific UDF so I have to change those plugins and implement it another way?

Thanks

 
8 years ago Sergei Golubchik
Re: Storage engine support and compatibility constraints
  • The documentation starts here. In the source code, plugin APIs are here. Although I don't see how you can check the compatibility manually.
  • You can reasonably expect that any UDF or a plugin present in a specific MariaDB version will not disappear if you upgrade to the next minor version. And it is unlikely to disappear if you upgrade to the next major version. We treat backward compatibility rather seriously and don't remove features lightly.
 
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.