From 8cb28e3ac9dd857fbd826be1ca4f9bbfea2124f7 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Mon, 5 Dec 2011 11:33:06 +0200 Subject: Handle microsecond resolution in PostgreSQL Qt date-time mappings --- NEWS | 4 ++++ doc/manual.xhtml | 7 ------- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/NEWS b/NEWS index e041b26..61f35ed 100644 --- a/NEWS +++ b/NEWS @@ -34,6 +34,10 @@ Version 1.7.0 get object id without loading the object. For more information, refer to Section 4.4 "Query Result" in the ODB manual. + * Support for microsecond precision in the Boost and Qt date-time types + mapping to PostgreSQL date-time data types. Additionally, Qt QDateTime + values stored in a PostgreSQL database can now be before UNIX epoch. + Version 1.6.0 * New concept, view, is a C++ class that embodies a light-weight, read- diff --git a/doc/manual.xhtml b/doc/manual.xhtml index 8296aea..72c1ce3 100644 --- a/doc/manual.xhtml +++ b/doc/manual.xhtml @@ -14206,13 +14206,6 @@ class Person QDateTime types are stored as a NULL value if their isNull() member function returns true.

-

Some valid Qt date-time values cannot be stored in a PostgreSQL database. - An attempt to persist a QDateTime value representing a - negative UNIX time (any point in time prior to the - 1970-01-01 00:00:00 UNIX time epoch) as a PostgreSQL - TIMESTAMP will result in the out_of_range - exception.

-

19.4.4 Oracle Database Type Mapping

The following table summarizes the default mapping between the currently -- cgit v1.1