-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unused modified
field on Upload
model
#1713
Conversation
485df0f
to
4ef2e71
Compare
migrations.AlterField( | ||
model_name='embargoedupload', | ||
name='created', | ||
field=django_extensions.db.fields.CreationDateTimeField(auto_now_add=True), | ||
), | ||
migrations.AlterField( | ||
model_name='upload', | ||
name='created', | ||
field=django_extensions.db.fields.CreationDateTimeField(auto_now_add=True), | ||
), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: this migration got created because TimeStampedModel
defines created
internally a bit differently using gettext_lazy
https://github.com/django-extensions/django-extensions/blob/main/django_extensions/db/models.py#L17
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
#1714 will fix the failing type check here. |
4ef2e71
to
ece150e
Compare
🚀 PR was released in |
I noticed this while investigating what new fields (if any) we need to add for garbage collection of
Uploads
. We don't use this anywhere at this time, and since we've already decided to rework how we domodified
(not usingTimeStampedModel
), I think it makes sense to just remove this.