From 2a12f87df3d130f0a376fe2dda4fc37c3ce9c51b Mon Sep 17 00:00:00 2001
From: Olav Morken <olav.morken@uninett.no>
Date: Tue, 1 Jul 2008 09:26:20 +0000
Subject: [PATCH] Consent documentation: Update for postgresql.

git-svn-id: https://simplesamlphp.googlecode.com/svn/trunk@734 44740490-163a-0410-bde0-09ae8108e29a
---
 docs/source/simplesamlphp-advancedfeatures.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/source/simplesamlphp-advancedfeatures.xml b/docs/source/simplesamlphp-advancedfeatures.xml
index bbbaec7e2..1968a2caa 100644
--- a/docs/source/simplesamlphp-advancedfeatures.xml
+++ b/docs/source/simplesamlphp-advancedfeatures.xml
@@ -442,7 +442,7 @@ foreach($_SERVER as $key=&gt;$value) {
       <title>Consent storage setup</title>
 
       <para>Consent storage requires a database to store the consent
-      information in. Currently, only MySQL is tested and known to work. The
+      information in. MySQL and PostgreSQL are tested and known to work. The
       consent will be stored in a table named <literal>consent</literal>. This
       table can be created with the following command:</para>
 
@@ -450,9 +450,9 @@ foreach($_SERVER as $key=&gt;$value) {
   hashed_user_id varchar(128) NOT NULL,
   service_id varchar(128) NOT NULL,
   attribute varchar(128) NOT NULL,
-  consent_date datetime NOT NULL,
-  usage_date datetime NOT NULL,
-  PRIMARY KEY USING BTREE (hashed_user_id, service_id)
+  consent_date timestamp NOT NULL,
+  usage_date timestamp NOT NULL,
+  PRIMARY KEY (hashed_user_id, service_id)
 );</programlisting>
 
       <para>Consent storage is controlled by the following options in
-- 
GitLab