Repository navigation
fix(grid): staged edits cannot hit the wrong row when a column is aliased to a key name (#1772) - #1803
Merged
Conversation
… an expression; a composite key needs every column (#1772)
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.
Closes #1772.
sqlResultGridSaveEnablednow also reads the select list: a primary key counts only when the result has it as a plain column of the table (id,t.id,\"id\",id AS id) or the list holds a*.SELECT number AS id, name FROM t,id + 0 AS idorCAST(number AS int) AS idno longer enable Save (an UPDATE keyed on thatidcould change another row, and the one-row check passes when the value matches exactly one).TableMutationEngine._hasMatchingPrimaryKeyuseseveryinstead ofany, so the preview warns when only part of a composite key is selected.