Repository navigation
v4.0.0-rc.4 - #474
Merged
Merged
v4.0.0-rc.4#474
Conversation
This file contains hidden or 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
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.
Fourth release candidate of 4.0.0, published with the npm dist-tag
next.4.0.0-rc.4.upsertGraph()patches a key it changes before the rows that read it (upsertGraph(): write a key that another place patches after the patch #428); keeps the other values of a JSON column it relates a row through (upsertGraph() overwrites a JSON column when it relates through a key in a JSON path of it #415); relates aBelongsToOneRelationmodel by its key alone; throwsInvalidGraphfor a#refat the root; faster cell lookups; documents more limits.patch(),merge()andrelate()write JSON paths intoNULLJSON columns. Typings: autocompletion and strict-mode fixes. Test databases moved out of the ephemeral port range.Part of #53.