[Python-modules-commits] [sqlobject] 02/02: Fix version in NEWS. Add note about old python-mysqldb versions and microseconds

[Neil Muller]

This is an automated email from the git hooks/post-receive script.

drnlmza-guest pushed a commit to branch master
in repository sqlobject.

commit e94fa79fbe7274ec07708539da8993c11d861582
Author: Neil Muller <drnlmuller+debian at gmail.com>
Date:   Fri Oct 30 20:18:37 2015 +0200

    Fix version in NEWS. Add note about old python-mysqldb versions and microseconds
---
 debian/NEWS | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/debian/NEWS b/debian/NEWS
index 22f7ba4..982bcdf 100644
--- a/debian/NEWS
+++ b/debian/NEWS
@@ -1,4 +1,4 @@
-sqlobject (2.1.2-1) UNRELEASED; urgency=low
+sqlobject (2.1.2-1) unstable; urgency=low
 
   Starting with SQLObject 2.0, DateTimeCol and TimeCol can read and write
   values with microseconds.
@@ -12,6 +12,9 @@ sqlobject (2.1.2-1) UNRELEASED; urgency=low
   using only second precision. The database can be manually updated to support
   microseconds.
 
+  For microsecond support using MySQL or MariaDB, both the database and the
+  python-mysqldb client need to be new enough. Versions of python-mysqldb
+  before 1.3.1 don't support datetime columns with microseconds correctly.
   Microseconds are supported by MariaDB since version 5.3.0 and by MySQL since
   version 5.6.4, and even these versions require special handling: columns to
   store microseconds have to be declared with precision 6: TIME(6),

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/python-modules/packages/sqlobject.git