[evennia] push by griatch - MySQL<v5.6.4 does not support millisecond precision in its DATETIME fi... on 2013-05-14 17:16 GMT
2 views
Skip to first unread message
eve...@googlecode.com
May 14, 2013, 1:16:16 PM5/14/13
to evennia...@googlegroups.com
Revision: c897d3180724
Branch: default
Author: griatch
Date: Tue May 14 10:15:58 2013
Log: MySQL<v5.6.4 does not support millisecond precision in its
DATETIME fields (as opposed to other databases). This meant that
Attributes, which do rely on millisecond precision for creating their
object hashes, got out of sync in a horrible way on MySQL (Issue 362). This
revision fixes the problem by going to second-level precision if a too-low
version of MySQL is detected (this should not be an issue since mysql does
not reuse its pks anyway).
http://code.google.com/p/evennia/source/detail?r=c897d3180724
Modified:
/src/server/manager.py
/src/utils/dbserialize.py
Branch: default
Author: griatch
Date: Tue May 14 10:15:58 2013
Log: MySQL<v5.6.4 does not support millisecond precision in its
DATETIME fields (as opposed to other databases). This meant that
Attributes, which do rely on millisecond precision for creating their
object hashes, got out of sync in a horrible way on MySQL (Issue 362). This
revision fixes the problem by going to second-level precision if a too-low
version of MySQL is detected (this should not be an issue since mysql does
not reuse its pks anyway).
http://code.google.com/p/evennia/source/detail?r=c897d3180724
Modified:
/src/server/manager.py
/src/utils/dbserialize.py
Reply all
Reply to author
Forward
0 new messages