#10398: It may cause error in django.db.backends.last_executed_query.
---------------------------------------------------+------------------------
          Reporter:  bear330                       |         Owner:  nobody     
               
            Status:  new                           |     Milestone:             
               
         Component:  Database layer (models, ORM)  |       Version:  1.0        
               
        Resolution:                                |      Keywords:  unicode 
pickle db backends
             Stage:  Accepted                      |     Has_patch:  0          
               
        Needs_docs:  0                             |   Needs_tests:  0          
               
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Changes (by mtredinnick):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * component:  Uncategorized => Database layer (models, ORM)
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Wrapping things in a try...except block isn't a particularly nice
 solution. It hides the problem by throwing away all the data. Better to
 use "errors='replace'" in the unicode conversion.

 At the same time, we might move the parameters away from being substituted
 into the query, since that always leads to confusion. Then we can document
 that parameters are a "best attempt" at being represented.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10398#comment:1>
Django <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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to