It should be possible to use a "RETURNING" clause to get the new row even in the instance of a get_or_create.
I occasionally use an UPDATE ... RETURNING query with Manager.raw to update a table and get modified instances in one shot. On Tuesday, January 12, 2016 at 12:54:03 PM UTC-6, bliy...@rentlytics.com wrote: > > After thinking about it a bit, I think the only function that would really > benefit from this would be the update_or_create. If you're doing > get_or_create you still need a second query to get the actual row. > > On Friday, January 8, 2016 at 4:13:26 PM UTC-8, bliy...@rentlytics.com > wrote: >> >> Hey Guys, >> >> Postgres 9.5 has added the functionality for UPSERT aka update or >> insert. Any interest in aligning UPSERT on the db layer with the >> get_or_create or update_or_create functionality in django? Sounds like my >> company would be interested in doing the work if the PR will get the >> traction. >> >> -Ben >> > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2b8db682-1b8d-4549-8d8c-f99f3d6b8f90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
