| 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 08:22:20 |
| Message-ID: | m2sj30dsg3.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:
>> > 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…
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2013-04-09 08:30:28 | Re: Call for Google Summer of Code mentors, admins |
| Previous Message | Dave Page | 2013-04-09 08:21:59 | Re: Heroku early upgrade is raising serious questions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2013-04-09 08:30:28 | Re: Call for Google Summer of Code mentors, admins |
| Previous Message | Hannu Krosing | 2013-04-09 07:42:29 | Re: Inconsistent DB data in Streaming Replication |