On 12/05/2014 07:59 AM, Robert Haas wrote: > I think it's probably an important distinction, for the kinds of > reasons Anssi mentions, but we should look for some method other than > a system column of indicating it. Maybe there's a magic function that > returns a Boolean which you can call, or maybe some special clause, as > with WITH ORDINALITY.
I thought the point of INSERT ... ON CONFLICT update was so that you didn't have to care if it was a new row or not? If you do care, it seems like it makes more sense to do your own INSERTs and UPDATEs, as Django currently does. I wouldn't be *opposed* to having a pseudocolumn in the RETURNed stuff which let me know updated|inserted|ignored, but I also don't see it as a feature requirement for 9.5. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
