#3492 closed (fixed)
[patch] db.backends.postgres chokes on unicode extra
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Keywords: | unicode postgresql unicode-branch | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
If you use unicode in Model.objects.extra(...), postgres chokes.
For instance when using Form.clean_data from newforms.
Attachments (1)
Change History (6)
Changed 16 years ago by
Attachment: | postgresql_unicode_extra_fix.patch added |
---|
comment:2 Changed 16 years ago by
Triage Stage: | Unreviewed → Design decision needed |
---|
This is for psycopg1. Related for mysql: #3492. It should probably be solved for all backends ... See discussion in django-developers
comment:3 Changed 16 years ago by
Keywords: | unicode-branch added |
---|
This has been fixed in the unicode branch (tested with all backends) as part of the wider fixes there. I've added the test from this patch in [5243] and will close this ticket once the unicode branch is merged into trunk.
comment:4 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Fixes a bug when using unicode in extra query