#20010 closed Bug (fixed)
Tests for CaptureQueriesContext fail under Oracle
| Reported by: | Aymeric Augustin | Owned by: | Simon Charette |
|---|---|---|---|
| Component: | Testing framework | Version: | dev |
| Severity: | Release blocker | Keywords: | |
| Cc: | Florian Apolloner | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
These tests were introduced in 952ba5237ea62e7647cdd5214b1df79c0e7cea38. They rely on query parameters being listed in connection._last_executed_query, which doesn't appear to be true under Oracle.
Two solutions:
- change the tests for
CaptureQueriesContext - change
_last_executed_queryto be more like SQLite
Attachments (1)
Change History (11)
comment:1 by , 13 years ago
| Cc: | added |
|---|
comment:2 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
by , 13 years ago
| Attachment: | 0001-Fixed-20010-Make-sure-last_executed_query-contains-i.patch added |
|---|
comment:4 by , 13 years ago
| Has patch: | set |
|---|
comment:5 by , 13 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Tests pass with this patch under Oracle.
Do you think it's useful to add a line in the "backwards incompatible changes" section of the release notes?
comment:7 by , 13 years ago
Wondering if it's worth it, the change to SQLite3 wasn't documented AFAIK 6605ac331a9e03fa41c301d122c5727c0d98b970.
comment:9 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I guess I should fix my own mess. I think I'll favor the behave-more-like-SQLite approach.