X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F257A3A5BC9 for ; Thu, 27 Jan 2005 15:46:34 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76101-07 for ; Thu, 27 Jan 2005 15:46:26 +0000 (GMT) Received: from smtp210.tiscali.dk (smtp210.tiscali.dk [62.79.79.113]) by svr1.postgresql.org (Postfix) with ESMTP id 527AB3A5B2C for ; Thu, 27 Jan 2005 15:46:29 +0000 (GMT) Received: from cpmail.dk.tiscali.com (mail.tiscali.dk [212.54.64.159]) by smtp210.tiscali.dk (8.12.6p3/8.12.6) with ESMTP id j0RFkRGJ001297 for ; Thu, 27 Jan 2005 16:46:28 +0100 (CET) (envelope-from cpp@world-online.no) Received: from [129.240.251.142] by cpmail.dk.tiscali.com with HTTP; Thu, 27 Jan 2005 16:46:25 +0100 Date: Thu, 27 Jan 2005 16:46:25 +0100 Message-ID: <41C17A7100006F65@cpfe4.be.tisc.dk> From: cpp@world-online.no Subject: Need SELECT rights to UPDATE/DELETE WHERE? To: pgsql-sql@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=2.06 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, NO_REAL_NAME, RCVD_IN_BL_SPAMCOP_NET X-Spam-Level: ** X-Archive-Number: 200502/10 X-Sequence-Number: 20121 PostgreSQL 8.0.0 on WinXP Pro, libpq In my hands it looks like a user with INSERT/DELETE/UPDATE rights on tabl= e1 cannot do "update table1 set field1=3Dxx where field2=3Dyy" without also = being granted select rights. However, the user can do "update table1 set field1= =3Dxx". Is this right? Any explanations why it should be like this and any sugges= tions on how to get around it without granting select is greatly appreciated. KP