#25626: Storing big strings with special chars fails when using PostgreSQL with
SQL_ASCII encoding
-------------------------------------+-------------------------------------
Reporter: JoseTomasTocino | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
[https://docs.djangoproject.com/en/1.8/ref/databases/#encoding As
documented], "Django assumes that all databases use UTF-8 encoding. Using
other encodings may result in unexpected behavior such as “value too long”
errors from your database for data that is valid in Django."
--
Ticket URL: <https://code.djangoproject.com/ticket/25626#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.bcaca2e9ed04bab1f40a418f5da709b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
