-
Notifications
You must be signed in to change notification settings - Fork 50
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
Let IntegerVersionField starts with '1' #150
Comments
|
Yes. It was a mistake while copying the code. It is AutoIncVersionField. Agreeing to your point that - concurrency is a low level system that should not be exposed to the business logic. There is no harm in version getting initialized with 2 while creating a model with version with value 2. Thought the expected behavior of AutoIncVersionField is always to increment by 1. |
yep, probably is true and I keep this issue opened as |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Suppose we have a model,
If we create the object using create, we are getting the expected version value(which is 1).
But instead of that if we create the model using the initializer and create it using the save() method. The version is 2.
The text was updated successfully, but these errors were encountered: