diff options
author | Carlos Garnacho <carlosg@gnome.org> | 2021-04-07 11:27:56 +0200 |
---|---|---|
committer | Carlos Garnacho <carlosg@gnome.org> | 2021-04-07 23:27:45 +0200 |
commit | 3028e54d7432accdfcb43bc79f52fcd474e9eb82 (patch) | |
tree | 6a3ebb90a5cd8610f281282fd1116d951adde6b5 /docs | |
parent | bb45e4f0f2bb04f400f17a0fa5316906ba09b5bb (diff) | |
download | tracker-3028e54d7432accdfcb43bc79f52fcd474e9eb82.tar.gz |
docs: Change lower datetime bound in doc/tests about limits
Although SQLite supports dates starting from year 0000-01-01 (1 BC
in ISO8601 parlance), we are porting to using GDateTime internally
which changes the lower boundary to 0001-01-01.
This date range change is unlikely to have real life consequences,
and OTOH using GDateTime allows us to drop our own ISO8601 parsing
and architecture dependent code, which has larger consequences with
eg. 32-bit time_t.
Diffstat (limited to 'docs')
-rw-r--r-- | docs/reference/libtracker-sparql/limits.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/reference/libtracker-sparql/limits.xml b/docs/reference/libtracker-sparql/limits.xml index 6119fe9ac..4e269cf5f 100644 --- a/docs/reference/libtracker-sparql/limits.xml +++ b/docs/reference/libtracker-sparql/limits.xml @@ -126,7 +126,7 @@ <para> Integers are 64 bit wide. Floating point numbers have IEEE764 double precision. Dates/times have microsecond precision, and may - range between 0000-01-01 00:00:00 and 9999-12-31 23:59:59. + range between 0001-01-01 00:00:00 and 9999-12-31 23:59:59. </para> </sect2> </part> |