Should I use MySQL 6.0 for my large project? - mysql

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.

Related

mysql installation on SUSE 15 Failing with : Problem: nothing provides 'libc.so.6(GLIBC_2.28)(64bit)'

Im trying to install mysql on SUSE 15 Sp2 :
Followed steps from official documentation :
https://dev.mysql.com/doc/mysql-sles-repo-quick-guide/en/
But when i tried to install the mysql getting following error :
Problem: nothing provides 'libc.so.6(GLIBC_2.28)(64bit)' needed by the
to be installed mysql-community-server-8.0.29-1.sl15.x86_64
Solution
1: do not install mysql-community-server-8.0.29-1.sl15.x86_64
Solution 2: break mysql-community-server-8.0.29-1.sl15.x86_64 by
ignoring some of its dependencies
According to the list of platforms that are supported by this version of MySQL, version 15.3 of openSUSE is required. That's probably what's going wrong here: The version of glibc which is provided by the repositories of your openSUSE 15.2 is too old for this MySQL version. If possible, I would recommend you backup your system and then upgrade to 15.3 and then to 15.4, see these instructions. Especially when you intend to do development, it's really wise to first upgrade your OS to the latest version, because only then will you have the latest versions of the technologies you're learning – otherwise, some things you learn will be outdated from day one.

MYSQL Backward compatible to 5.1.1?

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.

Typo3 7.6 MySQL Version

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.

What version of MySQL should I use for a CRM?

I've read through a number of pages detailing the version differences between the different MySQL versions, but none of them have given me a real clear picture as to what is best for the application I am making. I'm in the process of building a CRM which will handle 20,000 customers at launch and built on a LAMP stack. The OS will either be CentOS or FreeBSD.
Right now for test purposes we've been using a MySQL 5.0 server for the database, but we are wondering which version we should use for production. If anyone could give some thoughts as to the pros and cons of using 5.0 vs 5.1 vs 5.5 vs 5.6 in the context of a CRM application, it would be most appreciated.
TL;DR 5.5
For a new software rollout, it makes sense to integrate and do final testing with the latest generally available (GA) release of your infrastructure components.
Right now that's 5.5.20 of the MySQL community server. 5.6.x is considered a development release. It probably doesn't make sense for you to try to do integration and final testing with such a release, unless it offers a new feature that's a critical success factor for your new software. (But then you should ask yourself whether it makes sense to make your product dependent on exotic new features in unfinished dbms releases.)
EDIT... #rkosegi has a good point. If you're going to deploy on an enterprise grade linux server distro like Red Hat Enterprise Linux (rhel) use the version it supports. 5.1 works fine.
I think better you should use v5.1.XX because it's in active development state and stable too.
MySQL has stopped working on v5.0 i guess extend support also will expire soon.
http://dev.mysql.com/doc/refman/5.0/en/

Is MySQL Connector/Net backward compatible?

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!).