On Mar 18, 2013, at 4:50 PM, Russell Keith-Magee wrote: > Summary - if you issue a SELECT query that contains an "WHERE X IS NONE" > clause, and nothing matches the SELECT, and an object was inserted by the > last statement, the SELECT query returns *the primary key of the object that > was recently inserted*, not an empty result set. Anyone who can rationalize > this behavior without resorting to medicinal grade hallucinogens wins a shiny > new penny.
You know what's great? There's lots of code out there that expects this behavior. In fact, there are (sometimes) complaints from people moving from MySQL that PostgreSQL doesn't work that way. I weep for humanity. -- -- Christophe Pettus x...@thebuild.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
