| From: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: MERGE Specification |
| Date: | 2008-04-21 20:38:06 |
| Message-ID: | 17C14E5B-A7F0-435A-9059-272731E5E474@themactionfaction.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 21, 2008, at 4:08 PM, Simon Riggs wrote:
> The following two files specify the behaviour of the MERGE statement
> and
> how it will work in the world of PostgreSQL. In places, this
> supercedes
> my recent commentary on MERGE, particularly with regard to triggers.
>
> Neither of these files is intended for CVS.
>
> The HTML file was generated from SGML source, though the latter is not
> included here for clarity.
>
> The test file shows how I expect a successful test run to look when a
> regression test is executed with a working version of final MERGE
> patch
> applied. It has behavioural comments in it also, to make it slightly
> more readable.
>
> If anybody has any questions, ask them now please, before I begin
> detailed implementation.
"MERGE will not invoke Rules." Does this imply that MERGE cannot be
used on views or that the resulting INSERTs or UPDATEs do not work on
views?
Cheers,
M
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2008-04-21 20:38:15 | [Pljava-dev] stack depth limit exceeded - patch possible? |
| Previous Message | Andrew Dunstan | 2008-04-21 20:21:53 | column level privileges |