The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-15. For the latest, interactive version please visit https://mariadb.com/kb/.

Visual Studio - MariaDB - Entity Framework 6+

Dear Specialists,

We can use at the moment "Visual Studio ADO.NET Driver for MySQL" (https://www.mysql.com/products/connector/) and also there was lots of work done with Visual Studio Integration for MySQL. (http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio.html).

The question is while now it is compatible with MariaDB and I can use MariaDB instead of MySQL, how long if at all there will be a point when this won't become anymore compatible.

Is this connection compatibility related with a core or some layer in MariaDB which doesn't change and so it should be working in the future.

The reason I am asking is to decide with the strategy. I am testing MariaDB with Entity Framework and the driver/connection mentioned above and it is working but what if you deviate from the connectivity at certain point?

Thank you.

Answer

We plan to stay protocol compatible with MySQL. While we have introduced few protocol extensions, the protocol is fully backward compatible.

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.