February 19th, 2005, 01:10 PM
version 5.5 is the current version -- PLEASE READ THIS IF YOU'RE NOT ON 5.0 YET
mysql version 4.1 has been in production status since october, 2004
if you're not on 4.1 yet, and you post a problem and wish to receive a solution involving sql, it is your responsibility to mention which version you're on
otherwise, you might get a solution using sql that works only in 4.1
EDIT: we've updated the thread to reflect that 5.5 is current, and you shouldn't post a question without mentioning your version if your version is below 5.0
Last edited by r937; September 27th, 2011 at 07:34 AM.
February 21st, 2005, 04:25 AM
If you haven't upgraded, what are you waiting for?
Some benefits of 4.1 which may help you decide:
SELECT * FROM table1 WHERE id1 IN
(SELECT id2 FROM table2 WHERE name = 'simon');
Show Warnings & Show Errors:
now you can actually work out what those errors are!
Now with 40 byte password hashes instead of 16 byte
Now just knowing the hash isn't enough to let a cracker in.
--Simon ('cos old software is bad software)
February 21st, 2005, 06:28 AM
well, if we're going to list 4.1 features, i think one of the spiffiest is the GROUP_CONCAT function
February 22nd, 2005, 09:13 AM
My favorite is the unicode support and how it was implemented. I just can't understand why data types like NCHAR, NVARCHAR, etc. exist after I see how MySQL did it. I'm sure there are reasons, I just can't conceive them right now. Oh well.
Oh, and the subqueries are especially nice when you're migrating from one DBMS to MySQL.
mysql> SELECT * FROM user WHERE clue > 0;
0 Results Returned.
My Tech Blog
June 21st, 2005, 12:15 AM
I like how easy it is to set character sets when creating tables. Made it very easy to add support for UTF-8, Shift_JS, Big5, etc to my program, so long as you also use the same character set for [phpnet=htmlentities]htmlentitites()[/phpnet] (when using PHP, obviously).
-- Cigars, whiskey and wild, wild women. --
June 21st, 2005, 12:37 AM
UTF-8 is super important for globalization.
Originally Posted by Sepodati
I'm just terribly affraid to switch from 4.0.20d to 4.1.x...
It looks like they made quite some change about Timestamp field and I'm not sure my applications will support it.
October 24th, 2005, 04:45 PM
October 24th, 2005, 04:53 PM
thanks simon -- subject changed
October 28th, 2005, 01:24 PM
Now MySQL 5.0 production release available !!!
Now is available the MySQL 5.0 for production, this is a great news for mysql friends.
MySQL 5.0 Features
October 31st, 2005, 03:10 PM
My main interest in version 5.0 is speed the improvements made to SELECT queries using OR.
April 25th, 2006, 01:53 PM
Ive recently upgraded from Mysql 4.1 to 5, and found very little problems with the change. The only real problem i found was that i had the odd field that was named on a reserve word in 5 but not in 4.1, so some queries broke.
Other than that, make sure you back your data up and do a table check after the upgrade.
Comments on this post
February 9th, 2007, 11:53 PM
I should note that MySQL recommends you dump and import your data when upgrading from 4.x to 5.0.
"MySQL recommends that you dump and reload your tables from any previous version to upgrade to 5.0."
So, simply dump all of your data with mysqldump from your old version. Perform your upgrade. Then, re-import your data into the new, upgraded version.
mysql -u root -p < dumpfile.txt
April 26th, 2007, 01:51 AM
The latest version available now is MySql 5.2.3 . Subject may be altered, if needed.
"Whatever the mind can conceive and believe, the mind can achieve."
Note that the above (5.2.x) and 5.1.x, are still Beta and are not recommended for Production use. For production, you should use the latest stable release of 5.0, which for the community is 5.0.41:
(as of May 19, 2007)