Hi, I'd like to propose a created_at / modified_at auto field to models so that one can just turn this functionality on by a setting in settings.py or within the models Meta settings. I want these fields on both of the OneToOne related models when using concrete inheritance, thus using a TimeStampedBaseModel abstract model would cause these fields to clash. The reason I need created_at / updated_at on every table because Django is not the only app using the database I have other services sharing the same database. I assume having created_at updated_at fields on tables to be very common. I can imagine django creating those fields to all tables implicitly while handling those field collisions properly (eg. When accessing model.created_at on a derived class it will return the value of that model. model.base_model.created_at would give access to its base model).
What are your thoughts? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4c2a341f-e9d1-4841-892d-8d72c7688db9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
