-
Notifications
You must be signed in to change notification settings - Fork 8
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
chore: add notice to readme #113
Conversation
README.md
Outdated
|
||
- since version 1.0.0 the default vaule of `stale` was set to `ok` in viewQuery. | ||
|
||
If the update condition field isn't `id` you must put `stale` in `options` parameter to make sure you get the correct data, like: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the update condition field isn't `id` you must put `stale` in `options` parameter to make sure you get the correct data, like: | |
If the update condition field isn't `id` you might need to set `stale` in `options` parameter to make sure you get the latest data if you have a strong need of data instant consistency, like: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think stale
must be set to 1 in a write operation. Otherwise, the dirty read and dirty write would happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
k, I got you, you are talking about write
, LGTM.
chore: rename History.md to History-obsoleted.md
No description provided.