#13354: Possible bug, or possible docs error.
---------------------------------------------------+------------------------
          Reporter:  orokusaki                     |         Owner:  nobody
            Status:  closed                        |     Milestone:  1.2   
         Component:  Database layer (models, ORM)  |       Version:  SVN   
        Resolution:  invalid                       |      Keywords:        
             Stage:  Unreviewed                    |     Has_patch:  0     
        Needs_docs:  0                             |   Needs_tests:  0     
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Comment (by orokusaki):

 One final note. You mentioned:

 >> The fact that a particular field's implementation of get_prep_value
 uses its to_python...

 This really matters because {{ to_python }} is provided in the docs as
 part of the '''public API''' to hook in your own functionality. It even
 gives specific details on how to ensure it's run each time. It's not
 simply a matter of behind-the-scenes implementation.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/13354#comment:4>
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-upda...@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