Update to MySQL 5.6.x

[thinksaydo]

I think Homestead (and Forge) could benefit from updating to the latest release of MySQL instead of the older version currently installed by default. Yes, we could update this ourselves, but the beauty of Homestead (and Forge) is the ease of local development without custom configuration.

Why MySQL 5.6? Speed: http://www.mysql.com/why-mysql/benchmarks/

What it takes to use the official Oracle Debian package instead of the outdated apt-get version: http://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/

I just attended an Oracle MySQL talk where the speaker encouraged everyone to be using 5.6 release now because of the dramatic performance improvements especially in InnoDB, with 5.7 on the horizon in March of 2015 with even faster performance.

Let me know if I can help with this in some way too.

[thinksaydo]

Looks like the VM MySQL install is done in laravel/settler, so I'll look into making a pull request on that repo in the next few weeks.

[xtrasmal]

Changes in MySQL 5.6.5 (2012-04-10, Milestone 8)
Previously, at most one TIMESTAMP column per table could be automatically initialized 
or updated to the current date and time. This restriction has been lifted. 
Any TIMESTAMP column definition can have any combination 
of DEFAULT CURRENT_TIMESTAMP and ON UPDATE CURRENT_TIMESTAMP 
clauses. In addition, these clauses now can be used with DATETIME column definitions. 

For more information, see Automatic Initialization and Updating for TIMESTAMP and DATETIME.

I'd like that too. Cause the MySQl version currently allows for one column with CURRENT_TIMESTAMP as a default or onUpdate.

[svpernova09]

Closing this issue as old and we've just reenabled issues on the Homestead Repo.

If you're still having issues please open a new issue and link to this issue. Thanks!