zzzeek / sqlalchemy_old / issues / #1940 - mysql 'timestamp default current_timestamp on update current_timestamp' doesn't reflect() properly — Bitbucket

Issue #1940 resolved

Former user created an issue 2010-10-07

Found a bug in the mysql _re_column regexp regarding timestamp "on update" behaviour.

Diff attached, pullable from https://bitbucket.org/taavi_burns/sqlalchemy (momentarily; want to include ticket number in changeset).

mysql_timestamp_on_update.diff

Comments (3)

Former user Account Deleted
Finally uploaded over lunch. :) https://bitbucket.org/taavi_burns/sqlalchemy/changeset/73d2d5673e01
- 2010-10-07T13:51:17+00:00
Mike Bayer repo owner
- changed status to resolved
f3c9c87a24a5b3e6da9a33702ceee433b01f4905
- 2010-10-20T17:45:14+00:00
Mike Bayer repo owner
- removed milestone
Removing milestone: 0.6.5 (automated comment)
- 2014-02-23T18:14:40+00:00
Log in to comment

Assignee: –

Type: bug

Priority: major

Status: resolved

Component: mysql

Milestone: –

Votes: 0

Watchers: 0

Jira: the preferred issue tracker for Bitbucket. Join the team!