ancient mysql utc_timestamp rule seems unnecessary

[Mike Bayer]

from https://github.com/zzzeek/sqlalchemy/pull/355

#!


commit a21dc3d
Author: Mike Bayer [e-mail]
Date: Wed Sep 10 21:09:04 2008 +0000

- the function func.utc_timestamp() compiles to UTC_TIMESTAMP, without
the parenthesis, which seem to get in the way when using in
conjunction with executemany().

we have a hardcoded UTC_TIMESTAMP render that seems unnecessary and gets in the way of parameters like fsp. the ancient assertion that this "gets in the way with executemany()" must be tested. It would only be some ancient mysqldb driver issue at best.

[Mike Bayer]

Remove MySQL UTC_TIMESTAMP rule

Removed an ancient and unnecessary intercept of the UTC_TIMESTAMP MySQL function, which was getting in the way of using it with a parameter.

Change-Id: I6e6b52c051418bcb9d31987e78299310810cb78d Fixes: #3966 (cherry picked from commit c0b85ad6ad1df2497a95c87d837c32d87f17291f)

→ <<cset 1729f4a05135>>

[Mike Bayer]

Remove MySQL UTC_TIMESTAMP rule

Removed an ancient and unnecessary intercept of the UTC_TIMESTAMP MySQL function, which was getting in the way of using it with a parameter.

Change-Id: I6e6b52c051418bcb9d31987e78299310810cb78d Fixes: #3966

→ <<cset c0b85ad6ad1d>>