There will be some postgresql specific features in Django 1.8 (at least array fields, probably also hstore, ranges and jsonb). There are also a couple of new features which have already landed which leverage postgresql specific features when present and fall back otherwise (uuid, interval).
I am in the process of working on some possible changes for how indexes are handled in Django[1] which would make the ability to refer to an index directly possible. >From a brief look at the code for create_or_update it seems reasonable we could inspect the connection and change the code path depending on whether it supports a more reliable approach. As we can also inspect the version (not just which database) I don't see any problem with the postgresql_psycopg2 backend only reporting that it supports_atomic_create_or_update if the version is sufficiently recent. So in my opinion, yes we would support it in a future version of Django, potentially not that far in the future. If we were to do so, we would also introduce support for the mysql version as well most likely. [1] https://github.com/django/deps/pull/6 On 28 September 2014 07:37, Simon Riggs <si...@2ndquadrant.com> wrote: > On 28 September 2014 00:01, Peter Geoghegan <p...@heroku.com> wrote: > > > I am a PostgreSQL major contributor, currently undertaking development > > of a feature sometimes called "UPSERT" for PostgreSQL. > > Thanks for posting this Peter. > > The feature is under review in the PostgreSQL community and we would > like to solicit open feedback about how such a feature might look and > what aspects make it more/less likely to be adopted by Django. > > Detailed feedback on ORM related issues is welcome. > > -- > Simon Riggs http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Training & Services > > -- > 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/CA%2BU5nMLBnfk7TNZSjeagzYG0bd2E_6nooErbYTx2jXp5R7U6bw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAMwjO1FUYCRMpON0din_wueHODDEFFt0TcpZ%3DBDdbgY6uSfeUA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
