We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To better distinguish between defined fields and internally created fields, 'pk' should be given a prefix _.
_
As statik grows, other internal fields will become necessary, and we need to avoid clashes with model field names.
The text was updated successfully, but these errors were encountered:
Note the existing pk needs to remain supported for backwards compatibility
pk
Sorry, something went wrong.
Rename 'pk' field to '_pk'
62ed298
Closes thanethomson#80
129de54
4ef7415
No branches or pull requests
To better distinguish between defined fields and internally created fields, 'pk' should be given a prefix
_
.As statik grows, other internal fields will become necessary, and we need to avoid clashes with model field names.
The text was updated successfully, but these errors were encountered: