Opened 17 years ago
Closed 17 years ago
#4758 closed (worksforme)
Oracle transaction doesn't rollbacks when deleting objects
| Reported by: | audial | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | unicode |
| Severity: | Keywords: | transaction oracle delete | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I use Oracle 10.2.0.1 with default config options.
When I try to delete objects this way:
Foo.objects.filter(...).delete()
and then fire the transaction.rollback() the changes are saved, so i have no objects in result (which i filtered).
No errors anywhere.
I've tested the same VIEW with the same settings.py file on PostgreSQL and all was ok.
Trunk also has this behavior.
Change History (2)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I assume this was about using TransactionMiddleware. I tested several scenarios against that, and it seems to be working as expected. I'll close this bug.
Note:
See TracTickets
for help on using tickets.
I wasn't able to replicate this using the latest trunk revision. Could you post an example that shows this problem in action?