Hello Simon and Christian, good point, making a particular connection read only would be even better than using a modified atomic.
This way, if I really do need to use a read only transaction, I could just simply wrap my view inside an atomic decorator like @transaction.atomic(using='readonly') On the PostgreSQL side it would simple require adjusting > get_new_connection[2] to pass the option to psycopg2's set_session[3]. > Yes, I believe that should work. We could also add the 'deferrable' flag this way easily. Many thanks, Andor -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANqAxHa810Zo6-0ZocV5Qj7a7242LC3%3DrHncMcUMNhhPqVjh-A%40mail.gmail.com.
