storage_engine MySQL

For complex topics that regular users would not be interested in. For power users and database administrators.
Post Reply
parljohn
Posts: 9
Joined: Tue Jan 11, 2011 6:56 pm

storage_engine MySQL

Post by parljohn » Mon Sep 26, 2016 12:06 pm

Can you please update the code to check the "default_storage_engine" variable instead of the "storage_engine" variable as it has been deprecated. We are trying to setup OD Central Management using MySQL 5.7 but can't update the db because of this check. We would also like to look at the all the replication benefits of switching to 5.7.

http://dev.mysql.com/worklog/task/?id=7148

User avatar
jsalmon
Posts: 1551
Joined: Tue Nov 30, 2010 12:33 pm
Contact:

Re: storage_engine MySQL

Post by jsalmon » Mon Sep 26, 2016 12:20 pm

We have not even started to officially support MySQL 5.6 yet but have several offices using it at their own discretion and have had positive results. Are the replication benefits that you are looking for in 5.7 present in 5.6?
The best thing about a boolean is even if you are wrong, you are only off by a bit.

Jason Salmon
Open Dental Software
http://www.opendental.com

parljohn
Posts: 9
Joined: Tue Jan 11, 2011 6:56 pm

Re: storage_engine MySQL

Post by parljohn » Tue Sep 27, 2016 10:50 am

There are actually a ton of benefits with 5.7, not the least of which is about a 33% increase in speed and efficiency. They also added more replication error controls and checks to keep replication working properly in power or disconnect events. None of these features exist in 5.6. I get that we'll be using it an our own risk and that's ok. With this issue we can't use it just because of the upgrade query check which would be an easy fix for you guys. I think it's also a good idea to change it in that the variable you are currently checking against was officially deprecated in 5.5 but officially removed in 5.7. It would keep you up the standards of the 5.5 platform, not just 5.7. Of course all just my opinion :) but it would help me a ton if you could change it. Let me know, thanks.
Current Query: SHOW GLOBAL VARIABLES LIKE 'storage_engine'
New Query: SHOW GLOBAL VARIABLES LIKE 'default_storage_engine'
easy peasy

User avatar
jsalmon
Posts: 1551
Joined: Tue Nov 30, 2010 12:33 pm
Contact:

Re: storage_engine MySQL

Post by jsalmon » Tue Sep 27, 2016 1:24 pm

I hope supporting MySQL 5.7 is as easy peasy as you make it sound. I'm very curious to hear about issues you come across in your 5.7 adventure but can't guarantee that we'll change the software to accommodate that particular version. We're still trying to catch up with 5.6 and are constantly finding little quirks due to changes MySQL made that we never anticipated causing an issue within Open Dental in the first place. The biggest problem so far has been figuring out smooth ways to upgrade databases for our users. :cry:

I'll go ahead and add it as a bug to stop using the deprecated global variable.
http://opendentalsoft.com:1942/ODBugTra ... .aspx#16.2
The best thing about a boolean is even if you are wrong, you are only off by a bit.

Jason Salmon
Open Dental Software
http://www.opendental.com

parljohn
Posts: 9
Joined: Tue Jan 11, 2011 6:56 pm

Re: storage_engine MySQL

Post by parljohn » Tue Sep 27, 2016 2:28 pm

Hey Jason,

Thanks a ton for posting that, and don't misunderstand, I stake no claim on suggesting it will be an easy transition to 5.7 :oops: I'm not sure what we'll run into, but I'm happy to help in the process and give the clients a better product in the end. Our first venture is to simply just use the central manager to access all the other databases that are still 5.5 but can't update it because of this bug. We'll start with that then move onto replication and test that out. I'll let you know if I find simple things to fix or bigger problems to consider once that bug fix is implemented for me. Thanks for the quick updates.

User avatar
jsalmon
Posts: 1551
Joined: Tue Nov 30, 2010 12:33 pm
Contact:

Re: storage_engine MySQL

Post by jsalmon » Wed Sep 28, 2016 9:20 am

The bug "Enhancement, fixed MySQL query that checks the database storage engine" has been committed and will be released with v16.3.10
The best thing about a boolean is even if you are wrong, you are only off by a bit.

Jason Salmon
Open Dental Software
http://www.opendental.com

Post Reply