From: Marcin Siodelski <marcin@isc.org>
Date: Wed, 11 Mar 2015 20:17:09 +0000 (+0100)
Subject: [3673] Updated Kea guide with the limitations for the SQL timestamps.
X-Git-Tag: trac3764_base~16^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=efe7294639b84e668a43d467adf92d04ac95023d;p=thirdparty%2Fkea.git

[3673] Updated Kea guide with the limitations for the SQL timestamps.
---

diff --git a/doc/guide/admin.xml b/doc/guide/admin.xml
index df48e44e8b..4de3c835c6 100644
--- a/doc/guide/admin.xml
+++ b/doc/guide/admin.xml
@@ -432,6 +432,22 @@ host    <replaceable>database-name</replaceable>    <replaceable>user-name</repl
         <!-- @todo: document PgSQL upgrade once they are implemented in kea-admin -->
       </section>
     </section> <!-- end of PostgreSQL sections -->
+    <section>
+      <title>Limitations related to the use of the SQL databases</title>
+
+      <para>
+        The lease expiration time is stored in the SQL database for each lease
+        as a timestamp value. Kea developers observed that MySQL database doesn't
+        accept timestamps beyond 2147483647 seconds (maximum signed 32-bit number)
+        from the beginning of the epoch. At the same time, some versions of PostgreSQL
+        do accept greater values but the value is altered when it is read back.
+        For this reason the lease database backends put the restriction for the
+        maximum timestamp to be stored in the database, which is equal to the
+        maximum signed 32-bit number. This effectively means that the current
+        Kea version can't store the leases which expiration time is later than
+        2147483647 seconds since the beginning of the epoch (around year 2038).
+      </para>
+    </section>
   </section> <!-- End of Database sections -->
 
 </chapter>