Re: [Django] #7634: Using auto_now or auto_now_add should raise a DeprecationWarning

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown Re: [Django] #7634: Using auto_now or auto_now_add should raise a DeprecationWarning

by Django-3 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

#7634: Using auto_now or auto_now_add should raise a DeprecationWarning
---------------------------------------------------+------------------------
          Reporter:  Alex                          |         Owner:  nobody
            Status:  closed                        |     Milestone:        
         Component:  Database layer (models, ORM)  |       Version:  SVN  
        Resolution:  wontfix                       |      Keywords:        
             Stage:  Accepted                      |     Has_patch:  1    
        Needs_docs:  0                             |   Needs_tests:  0    
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Changes (by jezdez):

 * cc: jedzez (removed)
 * cc: jezdez (added)

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