Different query counts under Oracle when savepoints are involved
|Reported by:||aaugustin||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||master|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
This is a follow-up on #20387, see comments 5 and 6.
In short, Oracle doesn't have RELEASE SAVEPOINT, which means transaction.commit_savepoint() doesn't do anything. As a consequence, connection.queries contains one less entry under Oracle than under other databases.
#20387 was fixed by hardcoding the difference into the tests. This ticket is about finding a more robust solution to the general problem.
Change History (4)
comment:2 Changed 12 months ago by Aymeric Augustin <aymeric.augustin@…>
- Resolution set to fixed
- Status changed from new to closed