Depending upon the architecture of your system and what methods you use to update the data, you might want to consider using a database trigger for this.
The issue with relying upon the save method is that there are many ways a table can be updated without causing the save method to be called. (e.g. bulk_update)
This means you need to decide:
Does there need to be a solid guarantee that those fields will be updated any time the model is updated?
Does there need to be a guarantee that the code field is only updated when some other field is changed?
Is there sufficient control over how that table or model is updated to ensure that only methods that call the save method are used?
So this is one of those issues that need to be looked at in the context of the overall system requirements.
If the pure-Django method is considered adequate, then just calling save on the desired instance is sufficient. I’m not sure what you’re trying to accomplish with using the update_or_create function. What benefit do you think that provides?
Both ‘code’ and ‘time_stamp’ fields need to be changed on each ‘update’. I am using update as a means to trigger the generate_code() for the code field and auto_now for the time_stamp field.
Yes, the sole purpose of the CodeVerify model is to store email verification parameters after which the information is redundant. I intend to implement a cleanup of orphaned records via a daily ‘time_stamp expiration’ using celery.
All I am trying to do is look for an existing record, and if it exists, then trigger an update of the code and time_stamp fields via the save() method, or, if it doesn’t exist, create a new record.