The use of 'user' as a column name no longer causes errors in SquirrelMail/PostgreSQL
authorpdontthink <pdontthink@7612ce4b-ef26-0410-bec9-ea0150e637f0>
Wed, 21 Jul 2010 07:24:37 +0000 (07:24 +0000)
committerpdontthink <pdontthink@7612ce4b-ef26-0410-bec9-ea0150e637f0>
Wed, 21 Jul 2010 07:24:37 +0000 (07:24 +0000)
git-svn-id: https://svn.code.sf.net/p/squirrelmail/code/trunk/squirrelmail@13965 7612ce4b-ef26-0410-bec9-ea0150e637f0

config/conf.pl

index 65966aab54a3673508012b28e5415fb9b2f342c2..13b6a70ab5a3a2ecc4aacc4a3bb290334a0d7d55 100755 (executable)
@@ -4162,9 +4162,7 @@ sub command94 {
 
 sub command95 {
     print "This is the name of the field in which you want to store the\n";
-    print "username of the person the prefs are for. It default to 'user'\n";
-    print "which clashes with a reserved keyword in PostgreSQL so this\n";
-    print "will need to be changed for that database at least\n";
+    print "username of the person the prefs are for. It defaults to 'user'\n";
     print "\n";
     print "[$WHT$prefs_user_field$NRM]: $WHT";
     $new_field = <STDIN>;