On 01/08/2016 05:13 PM, [email protected] wrote: > 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.
That'd be great! I can't see any reason why a good PR for that wouldn't be accepted. There's no reason to be using the ugly algorithms in `get_or_create` or `update_or_create` when native UPSERT is available at the DB level. Carl -- 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 [email protected]. To post to this group, send email to [email protected]. 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/569193B4.70508%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
