Opened 17 years ago
Closed 17 years ago
#5087 closed (fixed)
Error filtering on TextField when using Oracle backend
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | 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
Filtering on a TextField with the Oracle backend raises an error, because Oracle LOBs can't be compared directly inside a WHERE clause. This is especially problematic for the Admin interface, which uses a TextField foreign key in the history table. See the comments in #4186 for an example of this, but I'm opening a new ticket because this patch doesn't address the original bug of that ticket.
Attachments (2)
Change History (5)
by , 17 years ago
| Attachment: | oracle_textfield_lookup.diff added |
|---|
by , 17 years ago
| Attachment: | oracle_textfield_lookup.2.diff added |
|---|
comment:1 by , 17 years ago
| Triage Stage: | Unreviewed → Ready for checkin |
|---|
comment:2 by , 17 years ago
The patch looks reasonable and I've verified the tests pass on all the MySQL/PostgreSQL/SQLite backends. My vmware setup is hosed at the moment, so I can't test Oracle. Since that's your area anyway, Ian, I'm not too worried.
comment:3 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
New version that doesn't break everything -- I should know better than to submit patches when I don't have a test environment available