2👍
The easiest and most compatible way of doing this would be to write your own DB adapter that inherits from django’s default and overrides the methods so that you set your own isolation level.
1👍
That seems odd. AUTOCOMMIT isn’t a transaction isolation level. READ COMMITTED is PostgreSQL’s default, and you’d get READ COMMITTED behavior with either 1 or 2.
I think you’re looking for set_session([isolation_level,] [readonly,] [deferrable,] [autocommit]).
Do both current and future versions of Django make it hard to specify
these higher isolation levels because they cause huge problems in
practice?
As far as I can tell, the issues have more to do with MySQL and backward compatibility than with PostgreSQL. MySQL defaults to REPEATABLE READ; some Django developers think that READ COMMITTED behavior is not as thoroughly tested as it should be.
- [Django]-How to get access to context from Jinja2 extension
- [Django]-Difference between returning modified class and using type()
- [Django]-Django 1.9 url include AttributeError 'str' object has no attribute 'regex'
- [Django]-Humanizing django-tables2 output?