Using update_at field instead of create_at

[YemreGurses]

Hi,
If a user changes his/her vote, it's create time does not change. Is it more sense to use update_at instead of create_at?

[Gilbishkosma]

Hi @YemreGurses , create_at is used to store the DateTime when the user first time voted.
And update_at will be changed each time the user change his/her vote.
Both create_at and update_at has their own features.
And i think it is good to use update_at and create_at separately.

[YemreGurses]

Yea, thats better. My point was storing changed vote time and django-vote does not have that feature afaik.

[shellfly]

@YemreGurses In the beginning, this project doesn't support down vote, so one's vote record either exists with a created_at or been deleted. Since version 2.1.4 which down vote was supported, that's when one can update his/her vote record. So yes, that's one feature that can be added to this project.