From: kink Date: Tue, 4 Jul 2006 08:57:27 +0000 (+0000) Subject: db scheme for postgres is different from that for mysql, document that X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=ff67d9f6e50c9345aa90ae587ccd4820a02af9c6;p=squirrelmail.git db scheme for postgres is different from that for mysql, document that (instead of changing it - that could break stuff for no strong reason) git-svn-id: https://svn.code.sf.net/p/squirrelmail/code/trunk/squirrelmail@11352 7612ce4b-ef26-0410-bec9-ea0150e637f0 --- diff --git a/doc/db-backend.txt b/doc/db-backend.txt index 76f423aa..19488b18 100644 --- a/doc/db-backend.txt +++ b/doc/db-backend.txt @@ -114,6 +114,10 @@ administration plugin. The DSN should look something like: mysql://squirreluser:sqpassword@localhost/squirrelmail or pgsql://squirreluser:sqpassword@localhost/squirrelmail +Note that when using the above PostgreSQL schema, you also need to change +the prefs_user_field variable in config.php from the default 'user' to +'username'. + From now on all users' personal preferences will be stored in a database. @@ -130,12 +134,12 @@ field and 64KB (database BLOB field size) limit to value field. If interface tries to insert data without checking field limits, it can cause data loss or database errors. Table information functions -provided by Pear DB libraries are not accurate and some database +provided by Pear DB libraries are not accurate and some database backends don't support them. Since 1.5.1 SquirrelMail provides configuration options that set allowed field sizes. -If you see oversized field errors in your error logs - check your -database structure. Issue can be solved by increasing database field +If you see oversized field errors in your error logs - check your +database structure. Issue can be solved by increasing database field sizes. If you want to get more debugging information - check setKey() function