When the tracking parameter is set to an integer, it controls the number of previous versions of the field that will be stored in the database. This can be useful for auditing or for maintaining a history of changes to a field. The system will keep track of the previous versions of the field and make them available for inspection.

It's important to note that the tracking parameter will consume extra space in your database and may affect performance. The more versions you keep track of, the more space it will take. Also, it's important to consider the security implications of storing previous versions of sensitive dat

The versioned parameter must be set to True in order to use the tracking parameter. It allows the ORM to keep track of changes in the fields. This is an important feature when you want to keep history or audit changes on your dat

It's important to note that the tracking parameter only works with fields that are marked as versioned = True, and it's only available for the fields that are using the PostgreSQL databas

Also, when you set tracking =0, it means no version tracking will be done, and all the previous versions will be deleted from the database