From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal / proof of concept: Triggers on VIEWs |
Date: | 2010-08-14 22:22:34 |
Message-ID: | AANLkTikahtRm7qY4wa8Mje-wvHBaV_bkgq5WL-0DfBKS@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 14 August 2010 13:12, Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> wrote:
> On 2010-08-08 1:45 PM +0300, I wrote:
>>
>> On 8/8/2010 12:49 PM, Dean Rasheed wrote:
>>>
>>> For those migrating code from Oracle, providing this feature as-is
>>> might be valuable, since presumably they are not too concerned about
>>> these concurrency issues. Ideally we'd want to do better though.
>>
>> Yes, you might be right. This feature on its on can greatly simplify
>> what people now have to do to get triggers on views.
>
> This weekend I had the luxury of working with our VIEW system, and it seems
> like I greatly underestimated the power of this feature, even if the
> concurrency issues I've mentioned in this thread would be left unaddressed.
>
> I haven't looked at the patch yet (I plan to do so), but +100 for this
> feature.
>
Thanks for your feedback. I'd be interested in any ideas on the
concurrency issues.
> Should we expect a new patch any time soon?
>
I hope to look at this again tomorrow.
I'll try to post an updated patch then, with some real trigger code,
but without addressing any of the concurrency issues.
Regards,
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | KaiGai Kohei | 2010-08-14 23:51:13 | Re: security label support, part.2 |
Previous Message | Bruce Momjian | 2010-08-14 22:15:48 | Re: more personal copyrights |