I find it amusing how people like to use fancy words like DRY, without
explaining exactly how it applies.
I am not trying to argue for keeping auto_now, but I just don't see
what the fuss is about?
The lazy date thing seems more "un-DRY" to me that this. But then
again, why not have both? + the "default" value.
I can see perfectly coding up something like this:
class Document(models.Model):
created = Date.... (auto_now_add
modified = Date...(auto_now...
This way I can CLEARLY see which fields do waht. IMHO it is much
better than Inheriting from some super/meta/power-class or using some
smart-ass decorators. I mean how far can we go with those, and how
will it look?
@auto_now('modified')
@auto_add_now('created')
@permission..
@other_stuff
@christmas_tree
class Document(models.Model):
created = Date.... ()
modified = Date...()
OR:
class Document(ComplicatedParent, AnotherFunParent):
pass
ComplicatedParent(models.Model?):
created = Date.... ()
modified = Date...()
def save():
//with custom save logic...
This last one, is the Approach I actually took, and let me tell you -
it was not pleasant always going and trying to dig up the class
hierarchy to see which fields exactly this model has.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
