[Sqlalchemy-tickets] Issue #3136: MySQL doesn't accept timezone offsets in datetime literals (zzzeek/sqlalchemy)

[Will R. <iss...@bi...>]

New issue 3136: MySQL doesn't accept timezone offsets in datetime literals
https://bitbucket.org/zzzeek/sqlalchemy/issue/3136/mysql-doesnt-accept-timezone-offsets-in

Will Ross:

Datetime literals with a timezone offset ("+0000" or "-0500") are invalid in MySQL. The issue is more visible with MySQL 5.6 because STRICT_TRANS_TABLES was added to the default configuration, causing statements that worked in older versions to fail. If no tzinfo is given, the datetime works fine. I'd have submitted a patch for this, but I'm not sure where to look in the code. That and I'm not sure it's even an actual bug, or intended behavior for backends that don't support timezones being passed timezone aware objects.