#7751 closed (fixed)
Don't assume that connection.autocommit is a callable
| Reported by: | Leo Soto M. | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | dev |
| Severity: | Keywords: | jython, db-be-api | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
source:django/trunk/django/test/utils.py assumes that connection.autocommit is going to be a callable. This is not true for some backends where it is a property (basically all JDBC based backends, also PyODBC and cx_Oracle).
The attached patch fixes this by taking into account the case where autocommit is a property.
Attachments (1)
Change History (3)
by , 16 years ago
| Attachment: | autocommit.diff added |
|---|
comment:1 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [7940]) Fixed #7751 -- Added check to allow for the fact that autocommit can be a property, rather than a function on certain database backends. Thanks to Leo Soto for the fix.