On 07/09/10 16:16, Robert Gravsjö wrote:
>> with db.isolation(ISOLATION_SERIALIZABLE): >> # ... >> > > You don't want to serialize access to the database in a multi-user > application. Just in case: serializable transaction != serializing access - among serializable level transactions, the property of /looking like/ they occurred serially in some consistent order is supposed to be maintained. Maintaining that property may well result in quite a lot of actual serialization and transactions needing retries I suppose, depending on sophistication of the implementation. Anyway. Postgresql's "serializable" isn't "complete" presently, like oracle it's actually "snapshot" isolation: http://www.postgresql.org/docs/9.0/static/transaction-iso.html#MVCC-SERIALIZABILITY http://wiki.postgresql.org/wiki/Serializable http://en.wikipedia.org/wiki/Isolation_(database_systems)#SERIALIZABLE http://en.wikipedia.org/wiki/Snapshot_isolation Django doesn't currently have support for setting it AFAICS (and there's currently an assert restricting to level 0/1 in _set_isolation_level()), but maybe it would be sensible to add some support (not necessarily very fine-grained, perhaps just a django databases OPTIONS = {'isolation': 'snapshot'} a bit like 'autocommit' that means to use psycopg2 level 2|(0/2) instead of 1|(0/1) [autocommit off|on] for that database). 'snapshot' just being pedantic. 'serializable' would be consistent with postgresql/oracle usage of course. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
