Schema Cache Improvement 2 #5616
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #5616 +/- ##
==========================================
- Coverage 94.13% 94.13% -0.01%
==========================================
Files 129 129
Lines 9231 9235 +4
==========================================
+ Hits 8690 8693 +3
- Misses 541 542 +1
Continue to review full report at Codecov.
|
acinader
approved these changes
May 28, 2019
davimacedo
approved these changes
May 28, 2019
UnderratedDev
pushed a commit
to UnderratedDev/parse-server
that referenced
this pull request
Mar 21, 2020
* schema hasClass improvement * create object improvement * destroy object * update object * hasClass test rewrite * more tests * improve signing up users
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reduce the number of create/update/destroy object calls to cache.
After the class and fields have been validated and cached, no need to reload the schema from cache if already validated.
Create/Update/Destroy just does lookup from the cache.
I’m more than happy to answer any questions or would like feedback.