#3060: [patch] broken Timestamp on manual created Users using postgres/sqlite
--------------------------------------------------------------+-------------
Reporter: Ronny Pfannschmidt <[EMAIL PROTECTED]> | Owner:
adrian
Status: new |
Component: Contrib apps
Version: |
Resolution:
Keywords: |
Stage: Accepted
Has_patch: 1 |
Needs_docs: 0
Needs_tests: 1 |
Needs_better_patch: 1
--------------------------------------------------------------+-------------
Changes (by adrian):
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
Could we get a unit test that verifies this? Also, what exactly does
"broken timestamp" mean? Finally, I'm not in favor of the patch, because
{{{auto_now_add}}} is a hack that I'd like to get rid of eventually. If
nothing else, it should use {{{default=datetime.datetime.now}}}, taking
advantage of the callable default functionality.
--
Ticket URL: <http://code.djangoproject.com/ticket/3060#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
