[Python-modules-commits] [sqlobject] 01/01: Expand on news entry a bit

[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 4d17fc28479b6a529f2866927a0f6b9315e3fcea
Author: Neil Muller <drnlmuller+debian at gmail.com>
Date:   Fri Oct 30 16:24:59 2015 +0200

    Expand on news entry a bit
---
 debian/NEWS | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/debian/NEWS b/debian/NEWS
index c77fc1e..22f7ba4 100644
--- a/debian/NEWS
+++ b/debian/NEWS
@@ -3,10 +3,15 @@ sqlobject (2.1.2-1) UNRELEASED; urgency=low
   Starting with SQLObject 2.0, DateTimeCol and TimeCol can read and write
   values with microseconds.
 
-  Backward compatibility warning! Date/Time columns created with microseconds
+  Backward compatibility warning! Date/Time values created with microseconds
   cannot be read back from SQLite databases (and perhaps other backends) with
   versions of SQLObject older than 1.7.
 
+  SQLObject will not automatically switch to using microseconds for some
+  backends. In these cases, existing databases will continue to work as before,
+  using only second precision. The database can be manually updated to support
+  microseconds.
+
   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