I’ve just started using Umbraco for a charity that requires
highly available web sites but can’t afford enterprise (or even standard)
Microsoft SQL server licenses. We’ve been using .NET and MySQL on Linux for
years and have recently moved our front-end web servers from Apache/Mono to
IIS/.NET so Umbraco looked like a sensible choice for us.
So far our technical team is very impressed and it seems likely that
we’ll be using Umbraco for many projects and hopefully contributing back to the
community whenever possible.
However, we have found a lack of clarity about whether MySQL
will be supported in the long term.
I expect that the answer is that MySQL on Linux will be
supported in the long term and I appreciate that in a project like this there
are always differing opinions on priorities but the combination of the removal
of support from the latest stable release and my inexperience with Umbraco and the
community around it is causing a little concern to me and my colleagues so if
anyone can provide re-assurance that would be appreciated.
Is the problem in 6.0.1+ just a bug? Maybe we should be
checking only for lower_case_table_names
since lower_case_file_system
is always 0 on Linux? Either way, the advice to change the lower_case_file_system setting should be removed.
For the record, our Linux MySQL database server works fine
with Umbraco 6.0.0 (although we did have to take a roundabout route of
upgrading via 4.11.5 because a fresh install of 6 doesn't work). We have set
lower_case_table_names to 1 which works OK but it’s not an ideal solution.
MySQL support status
Hi,
I’ve just started using Umbraco for a charity that requires highly available web sites but can’t afford enterprise (or even standard) Microsoft SQL server licenses. We’ve been using .NET and MySQL on Linux for years and have recently moved our front-end web servers from Apache/Mono to IIS/.NET so Umbraco looked like a sensible choice for us.
So far our technical team is very impressed and it seems likely that we’ll be using Umbraco for many projects and hopefully contributing back to the community whenever possible.
However, we have found a lack of clarity about whether MySQL will be supported in the long term.
On the one hand, we have comments in https://groups.google.com/forum/#!topic/umbraco-dev/GWmCApX0v1k which imply a large scale revamp of fundamental Umbraco code will be required to get MySQL on Linux working (which by the way is surely the most common OS to run MySQL on?) and there are comments about the lack of importance of fixing MySQL bugs (http://issues.umbraco.org/issue/U4-1632) and recent commits that explicitly prevent the use of MySQL on Linux (SupportsCaseInsensitiveQueries in http://umbraco.codeplex.com/SourceControl/changeset/view/588a2c5773fa#src/Umbraco.Core/Persistence/SqlSyntax/MySqlSyntaxProvider.cs) but on the other hand the work to get Umbraco working on Mono / Linux appears to be receiving encouragement to the point that it is a highlighted feature at this year’s CodeGarden – surely we’re not intending to support Umbraco on Mono but require a Windows install of MySQL?
I expect that the answer is that MySQL on Linux will be supported in the long term and I appreciate that in a project like this there are always differing opinions on priorities but the combination of the removal of support from the latest stable release and my inexperience with Umbraco and the community around it is causing a little concern to me and my colleagues so if anyone can provide re-assurance that would be appreciated.
Is the problem in 6.0.1+ just a bug? Maybe we should be checking only for lower_case_table_names since lower_case_file_system is always 0 on Linux? Either way, the advice to change the lower_case_file_system setting should be removed.
For the record, our Linux MySQL database server works fine with Umbraco 6.0.0 (although we did have to take a roundabout route of upgrading via 4.11.5 because a fresh install of 6 doesn't work). We have set lower_case_table_names to 1 which works OK but it’s not an ideal solution.
Thanks,
Chris
is working on a reply...