I found out that this behaviour take place when i delete objects.
when i create a new one and save -> and then rollback - all is ok
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
I have no nested transaction-managed views.
One transaction and one view.
Its good idea to trace the queries on the server side, but i can't get
it for now. Digging to this way.
Farid
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
I have used transactions with postgresql database, and all is ok.
When I start testing with Oracle backend I get strange things. It
seems, that transactions are autocommited.
Oracle has no autocommit by default, it can be changed during the
session.
I use views tested on PostgreSQL, where transac
