| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | yazicivo(at)ttmail(dot)com (Volkan =?utf-8?B?WWF6xLFjxLE=?=) |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Permission Problem for DELETE |
| Date: | 2008-05-28 00:50:38 |
| Message-ID: | 16760.1211935838@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
yazicivo(at)ttmail(dot)com (Volkan =?utf-8?B?WWF6xLFjxLE=?=) writes:
> On Tue, 27 May 2008, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Well, you tested wrong then. It works as expected for me, which is
>> that you need SELECT if the query involves fetching any existing
>> column value:
> Pff... Sorry for the noise. (I created example table under a differrent
> schema than "public" to be able to test effects of schema priviliges to
> INSERT/UPDATE/DELETE commands, but I somehow forgot that detail later.)
> I updated the doc patch.
I applied a docs patch for this, though not exactly what you sent in.
Thanks for pointing out the omission.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Anderson | 2008-05-28 01:48:24 | Re: Bottom Posting |
| Previous Message | Gregory Williamson | 2008-05-27 23:41:14 | Re: Open Source CRM - Options? |