{"action":"opened","issue":{"url":"https://api.github.com/repos/carljm/django-model-utils/issues/247","repository_url":"https://api.github.com/repos/carljm/django-model-utils","labels_url":"https://api.github.com/repos/carljm/django-model-utils/issues/247/labels{/name}","comments_url":"https://api.github.com/repos/carljm/django-model-utils/issues/247/comments","events_url":"https://api.github.com/repos/carljm/django-model-utils/issues/247/events","html_url":"https://github.com/carljm/django-model-utils/issues/247","id":192626846,"number":247,"title":"TimeStampedModel improvement ideas","user":{"login":"ryanpineo","id":2896066,"avatar_url":"https://avatars.githubusercontent.com/u/2896066?v=3","gravatar_id":"","url":"https://api.github.com/users/ryanpineo","html_url":"https://github.com/ryanpineo","followers_url":"https://api.github.com/users/ryanpineo/followers","following_url":"https://api.github.com/users/ryanpineo/following{/other_user}","gists_url":"https://api.github.com/users/ryanpineo/gists{/gist_id}","starred_url":"https://api.github.com/users/ryanpineo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryanpineo/subscriptions","organizations_url":"https://api.github.com/users/ryanpineo/orgs","repos_url":"https://api.github.com/users/ryanpineo/repos","events_url":"https://api.github.com/users/ryanpineo/events{/privacy}","received_events_url":"https://api.github.com/users/ryanpineo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-30T17:20:43Z","updated_at":"2016-11-30T17:20:43Z","closed_at":null,"body":"Hi I think the behavior of the TimeStampedModel class is a little misleading / less useful because of the following:\r\n\r\n- modified is set even though the model was only saved once (when creating).\r\n- modified is different than created even though they were set at the same time.\r\n\r\nI propose two possible changes to the TimeStampedModel so it can be possible to tell whether or not a model was only created or created and later modified/updated.\r\n\r\n1. modified is set to null on create and only changed on subsequent saves.\r\n2. modified is set the the exact same value as created on create.\r\n\r\nIt seems like 1. is a better solution to me because that way the modified field and the AutoModifiedField aren't tied directly to the AutoCreatedField also existing on the model."}}
{"actor":{"display_login":"ryanpineo"}}