While TrinityCore does not officially support MySQL version >= 5.6, there is a way to get it up and running.
the above will work fine with mysql 5.6 / mariaDB 10 and TC.
this will NOT work with TC + mysql 5.6 / MariaDB 10 currently due to what +Machiavelli mentioned above.
Feel free to experiment with the setting to see what works and what doesn't.
my server is faster , Well not the server as of such more the way spells/casts e.t.c run in DB.
but would it not be better to turn "strict mode off " if the DB is Only used for TC ?
example = MySQL ver 5.5.33 x32 "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
but MySQL ver 5.1.9 x32 is "NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" knowing you do not support this version!
It seems that MySQL changes something in the most recent 5.6 updates.
While Trinity was working fine on 5.6.15, after updating to 5.6.19 I can't apply auth_database.sql, getting weird errors.
I didn't change the sql_mode, it's still "NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES".
I'll potter around a bit, hoping that I get it working and that I don't need to rollback the update.
Edit: The issue actually wasn't related to the update. It was fixed by this commit.