I setup a new site with Typo3 7.6. I set it up with a mysql 5.1 database. The requirement for that typo3 version is normally mysql 5.5+.
By now everything is running without any problems and our provider will update to the new mysql version in the next 2-3 month.
What could be problematic with the current mysql 5.1 version? As far is I tested it everything works fine.
There is no major problem using mysql 5.1 with typo3 7 but if you need to use SSL there was a bug reported in mysql5.1
against OpenSSL could be tricked not to check server certificates. (Bug #47320, CVE-2009-4028)
and InnoDB support integrated as plugin in 5.5 that adds improvement in performance when your application uses innnodb more so for Typo3 7 onwards better to use 5.5 other reasons are UTF-8 support enhancement.
But there are no crashing report running Typo3 7+ on mysql 5.1 as well.
Related
I currently have setup Joomla 3.9.3 on production with MYSQL 5.5.62, i would like to upgrade to 5.7 or 8.
Is joomla 3.9.x Compatible with MySQL 5.6, 5.7, 8. The official documentation states that joomla works with 5.5.X+. Though this may imply supporting of 5.6, but wonder why they have stated their support on a minor version rather than a major one like 5.5+
Just need a confirmation on the same and any official supporting documents if available
We've had a Joomla v3.9.4 site running on MySQL 5.7.25 for several months and all has been good. No issues with Joomla or the extensions we're running that I've noticed.
Good luck!
I have a Wordpress site that was developed on a server running the latest version of MYSQL, however, I've just found out the host server (BT) is running 5.1.1. and they have no plans to upgrade anytime soon.
Does anyone know if there is a way of converting the database so it runs on 5.1.1 with no issues caused re the site being built in the latest version of Wordpress?
If this is a massive issue, then I do have some alternative hosting options, but I'm hoping for a way forward re conversion - any geniuses out there?
Many thanks
I doubt that BT is running MySQL 5.1.1. That version was never released. It was an internal development milestone in 2005.
The first GA release of the 5.1 branch was 5.1.30 in 2008. The last 5.1 release was 5.1.73 in 2013. But after 2013, 5.1 has been in "sustaining support" which means they will not make any new versions or fixes.
You shouldn't deploy to a hosting site that still runs any 5.1.x version. A site that is so far behind is probably behind on other software too, and I would not be surprised if they have known security vulnerabilities.
Wordpress officially requires MySQL 5.6 or later, according to https://wordpress.org/about/requirements/.
You could try to test that by testing on MySQL 5.1 (assuming you can find an installation package of MySQL 5.1). Use mysqldump to export data from your 5.6 database server and then import that to MySQL 5.1. The output of mysqldump wraps newer syntax in special comments that will be ignored by older versions of MySQL Server.
Regardless, my recommendation is:
Find another hosting service running MySQL 5.6 or 5.7.
Develop and test your site with the same versions of all software (MySQL, PHP, Apache, etc.) that you will eventually deploy to.
Hi I believe there have been some similar topics regarding connector/ net not supporting server versions prior to 5.0.
I have been trying add in a connection to a database in visual studio 2013 and I am not able to connect due to the server version being 4.1.2 I am unable to upgrade this databases server as its out of my hands.
What I have done is follow the suggested answers which is downgrade the connector/ net prior to 5.0 and downgrade the mysql server to 4.1.
I have added in the reference and its still giving me the same error.
Can anyone suggest anything else I could try or may be missing?
Cheers guys I'm pretty desperate now!!
See MySQL Connector/Net Developer Guide - Connector/Net Versions. This document contains table that shows the .NET Framework version required, and the MySQL Server version supported by Connector/Net.
For MySQL Server 4.1 you may need to install Connector/NET v. 6.2 and .NET Framework 2.x
what you must do is, install a lower NuGet that supports the version you have of maria db, in my case, I install the MySql.Data.EntityFramework 8.0.11 and it will work without problem.
If I have a MySQL server 5.1, can I use all the onnectors from version 5.1 and above?:
Connector/Net 6.1
Connector/Net 6.0
Connector/Net 5.2
Connector/Net 5.1
Clicking http://dev.mysql.com/downloads/connector/net/ defaults to 6.0...
Yes it is, pretty much.. See the documentation. You can also confirm it by going to the download page of each connector and then clicking versions of MySQL on left side of the page (which is the documentation library). It doesnt load for versions prior to MySQL 5.0, but loads for all other versions.
The real caveat is .NET connector itself exhibits different behaviours with different versions. See for one such..
If it helps even partially: I am running MySql 5.1.33 (via an installation of wampserver), and am using Connector/Net 6.0.3.0 with no problems (so far!).
MySQL 6.0 is for production. Can I use it for database storage of a large project?
MySQL 5.1 is the latest stable version, I'd recommend sticking with that. 6.0 will be quite unstable at this point.
EDIT as of 2011-05-26 MySQL 5.5.12 is the latest stable version. See this link for the lastest stable version: http://dev.mysql.com/downloads/
MySQL 6.0 in this moment is a alpha version, so I suggest you to use the current stable release -> MySQL 5.1
Here you can find some info about the table size limit depending on operating System. MySQL has not internal limit.
Only if there are critical enhancements that your site requires. And even then I'd hold back and use workarounds until it at least gets to beta.
We tried to use the latest PHP and MySQL 5.1 with failure on an IIS7 machine. I am sure if you download the source of PHP and compile it, it would have support for 5.1, but out of the box it seems to support 5.0. So, we replaced 5.1 with 5.0 and everything worked flawlessly.
Short story is use what works well. I would try it in development and avoid it in production until everything works well.