On Thu, Oct 16, 2014 at 8:00 PM, Peter Geoghegan <p...@heroku.com> wrote: > Basically, it's difficult to make this work for technical reasons > precisely because what I have here isn't join-like. Can I easily > disallow "OLD.*" in a RETURNING clause (recall that we only project > inserted tuples, as always)? Even if you think that's okay, I'd rather > give an error message indicating that that makes no sense, which is > what happens right now.
Well OLD and NEW are also not joins yet we expose them this way. It always seemed like a hack to me but better one hack than two different inconsistent hacks, no? Independent of all that though. CONFLICTING() isn't clear to me -- conflicting is a relative property of two or more objects which are both (or all) conflicting with each other. Which one does "CONFLICTING" refer to here? -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
