On Jan 18, 12:54 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Basically, PostgreSQL is trying to be more standards compliant by > default, at the cost of slightly impacting backwards compatibility. You > might also want to look at escape_string_warning (setting it to false, > since the warnings will get annoying after a while). Long-term, we can > fix this in Django (to send more SQL-standard strings), but it's a > little fiddly, because we try to be fairly version neutral and obviously > not everybody's running 8.2.
Fix me, if I'm wrong, but I think that prepending all the strings in queries with `E' should fix the problem. Django always escapes strings and the E'...' construction in PostgreSQL was designed for this purpose. A simple patch (adding 5 lines to django.db.backends.postgresql.base), which in case of TEXT and *CHAR types prepends the value with the `E' character is everything that is needed for this to work. I may create a ticket on Django Trac and enclose the patch, however I'd like to know your opinion first. -- Michal Chruszcz http://mchruszcz.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
