Thank you Michael, the CAST works as you suggested.
Best,
Vitaly
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy-alembic+unsubscr...@googlegrou
I understand that -00-00 00:00:00 would be an invalid datetime, but
there is presently no way in sqlalchemy to distinguish between actual Null
and the "-00-00 00:00:00" value that mysql substitutes when it gets an
invalid datetime
--
You received this message because you are subscribed
On 8/6/15 5:40 PM, vitaly numenta wrote:
platform = mac os x yosemtite
sqlalchemy version = '0.9.4'
mysql version = 5.6.23
table definition:
CREATE TABLE `twitter_tweets` (
`uid` varchar(40) COLLATE utf8_unicode_ci NOT NULL,
`created_at` datetime NOT NULL,
`retweet` tinyint(1) NOT NULL,
platform = mac os x yosemtite
sqlalchemy version = '0.9.4'
mysql version = 5.6.23
table definition:
CREATE TABLE `twitter_tweets` (
`uid` varchar(40) COLLATE utf8_unicode_ci NOT NULL,
`created_at` datetime NOT NULL,
`retweet` tinyint(1) NOT NULL,
`lang` varchar(10) COLLATE utf8_unicode_ci
