Opened 11 months ago

#20420 new Cleanup/optimization

Different query counts under Oracle when savepoints are involved

Reported by: aaugustin Owned by: nobody
Component: Database layer (models, ORM) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: 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.

Attachments (0)

Change History (0)

Add Comment

Modify Ticket

Change Properties
<Author field>
as new
The owner will be changed from nobody to anonymous. Next status will be 'assigned'
as The resolution will be set. Next status will be 'closed'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.