On Sat, Sep 27, 2014 at 6:33 PM, Peter Geoghegan <p...@heroku.com> wrote:
> The statement-level trigger stuff (i.e. the idea that ON CONFLICT
> UPDATE never fires an UPDATE statement level trigger) is for
> consistency with user-defined rules, where we're really compelled to
> have INSERT...ON CONFLICT UPDATE just be seen as an UPDATE


Excuse me. I mean where we're really compelled to have INSERT...ON
CONFLICT UPDATE just be seen as an **INSERT**.

-- 
Peter Geoghegan

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAM3SWZRoP9%3D-cCJr9GwXmw7SM3THoNP9h2E_CRqc2M%2Bo9Thw%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to