Fix updating a record twice in one session #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When updating a record a second (or more) time(s) in the same session, the changes are not being saved to the fulltext search. It seems that the changes get cached the first time, and don't get updated on the fulltext model. Performing the refresh reloads the model from the DB. This will be slightly less efficient due to the DB access a second time, but it is probably worth the slight inefficiency to have expected behavior when updating your models.
Steps to replicate:
Restarting tinker in between updates does not result in the inconsistency.