3 ms·
For the effort to absorb "big changes" I would also weigh porting to PostgreSQL.
by spacemanmatt 12y ago
For the effort to absorb "big changes" I would also weigh porting to PostgreSQL.
- VLM 12y agoIts clickbait headline, or maybe they're going for outright sarcasm given how little is changing. Technically its true that the install process is a little different but not much, and theres some minor changes in user configuration. I've looked into it and the most exciting "DBA level" changes are YEAR(2) is finally utterly expunged, and there's some new reserved words "NONBLOCKING" and "OPTIMIZERCOSTS". Thats about as exciting as it gets. Its not transparent upgrade but its not like they're changing the default db engine to an embedded nosql engine, or changing the default char encoding to EBCDIC.
- morgo 12y agoI would say the biggest change is that the default SQL mode will be the equivalent to 5.6's ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER. This means that a number of statements that produced warnings (but proceeded) will now produce errors. I have some slides on it here: http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 (see slide 33 onwards).