From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Call for Google Summer of Code mentors, admins |
Date: | 2013-04-09 16:27:13 |
Message-ID: | m261zvbrfi.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
David Fetter <david(at)fetter(dot)org> writes:
> On Tue, Apr 09, 2013 at 10:22:20AM +0200, Dimitri Fontaine wrote:
>> David Fetter <david(at)fetter(dot)org> writes:
>> >> > UPDATE ... RETURNING OLD
>> > There are several more DML operations with odd inability to return
>> > rows, but UPDATE's the one that really stands out, and is a bite-sized
>> > chunk in the sense of having a relatively small scope of design and
>> > not touching parts of the system unless they use the new grammar.
>>
>> Which makes me think about having OLD and NEW "relations" available in
>> per statement triggers, too. Would that be a SoC sized projects? Maybe
>> if the relation is simply a SRF…
>
> Are you envisioning this as a common infrastructure to both?
I don't think so. Would happily be proven wrong, though :)
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-04-09 16:29:37 | Re: Heroku early upgrade is raising serious questions |
Previous Message | Douglas J Hunley | 2013-04-09 16:27:12 | Re: elephant logo in OFM format? |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2013-04-09 16:27:52 | Re: page 1 of relation global/11787 was uninitialized |
Previous Message | Dimitri Fontaine | 2013-04-09 16:25:59 | Re: [COMMITTERS] pgsql: Add sql_drop event for event triggers |