#4664: [unicode] UnicodeDecodeError with on postgresql 7.4 using psycopg1 
backend
on python 2.3
--------------------------------------------------+-------------------------
   Reporter:  Øyvind Saltvik <[EMAIL PROTECTED]>  |                Owner:  
mtredinnick     
     Status:  new                                 |            Component:  
Database wrapper
    Version:  unicode                             |           Resolution:       
           
   Keywords:                                      |                Stage:  
Accepted        
  Has_patch:  0                                   |           Needs_docs:  0    
           
Needs_tests:  0                                   |   Needs_better_patch:  0    
           
--------------------------------------------------+-------------------------
Changes (by mtredinnick):

  * owner:  adrian => mtredinnick
  * summary:  unicode: UnicodeDecodeError with on postgresql 7.4 using
              psycopg1 backend on python 2.3 => [unicode]
              UnicodeDecodeError with on postgresql 7.4 using
              psycopg1 backend on python 2.3
  * stage:  Unreviewed => Accepted

Comment:

 So for some reason your default client encoding is ASCII (possibly
 configured to be non-international friendly in postgresql.conf). You, or
 any other user, may not be in control of that, so we have to work around.
 It's going to be annoying to have to try and change this value, though. We
 don't know what is available on the server-side and things will go badly
 wrong (Django will crash, most likely) if we get it wrong.
 
 I don't have PostgreSQL 7.4 on any machine at the moment. Can you add a
 line just before line 97 (at the same indentation level that as line 97)
 that says
 {{{
 #!python
 cursor.execute("SET CLIENT_ENCODING to 'UNICODE'")
 }}}
 So you will have a "set client encoding" followed by "show client
 encoding". I want to see if the "set" takes effect. If so, we can try to
 set the encoding to UTF-8 if the client reports ASCII.
 
 (I may have the "UNICODE" string wrong. It isn't listed as an explicit
 option [http://www.postgresql.org/docs/7.4/static/multibyte.html in table
 20.2, here], but it looks like it should be supported. Try a few
 alternative strings if that doesn't work.)

-- 
Ticket URL: <http://code.djangoproject.com/ticket/4664#comment:3>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to