Simon Riggs wrote:
On Fri, 2008-04-25 at 10:03 +0300, Hannu Krosing wrote:
On Tue, 2008-04-22 at 00:24 +0100, Simon Riggs wrote:
On Mon, 2008-04-21 at 16:38 -0400, A.M. wrote:
"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?
Yes, that's right. Just like COPY. That seems fine to me because you're
likely to be doing a MERGE immediately after a COPY anyway, so the
restriction just continues.
May be the bulk data merging variant of MERGE to be used after initial
COPY should be a variant of COPY with special keyword(s) instead of
MERGE ?
That does sound like a good way of differentiating between the OLTP and
bulk loading cases.
I'll bear that in mind as we develop.
To me, a simple user, it'd be important that MERGE implementation does
not place any unpredictable restrictions. For example in Oracle you can
break any MERGE statement by placing a full text index on the table. So
I'd really expect a MERGE in PostgreSQL to be fine with views, rules,
tsearch, etc.
Just my 2 cent.
--
Best regards,
Hannes Dorbath
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
