#6434: auto_now and auto_now_add should me marked for soon-to-be-deprecated
--------------------------------------------+-------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: SVN
Resolution: | Keywords: datefield
auto_now auto_now_add
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
--------------------------------------------+-------------------------------
Changes (by mk):
* cc: [EMAIL PROTECTED] (added)
* keywords: datefield => datefield auto_now auto_now_add
* has_patch: 0 => 1
* needs_better_patch: 0 => 1
Comment:
Some documentation is included but it's _very_ lacking. As per the
discussion in a mailing list thread[1] I added
Auto[Add]{Date,DateTime,Time}Field classes to
django/db/models/fields/__init__.py
I think this functionality is used often and therefore might deserve a
place in Django proper.
[1]: http://groups.google.com/group/django-
developers/browse_thread/thread/4cd631c225cb4e52
--
Ticket URL: <http://code.djangoproject.com/ticket/6434#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
-~----------~----~----~----~------~----~------~--~---
