Studio 3.1.1: four corrections, three of them to what 3.1.0 broke - #225
Merged
Merged
Conversation
Found the day 3.1.0 shipped, by using it. - the double click on a table opens its data again - and had done nothing at all since the repair meant to fix it registered a handler on a route DoubleTapped does not travel; - it no longer opens the row as well; - a double click on the connection opens the tab that describes the database, which is the same rule rather than a fourth exception; - the context menu draws no rule with nothing beside it, on any of the fourteen kinds of node; - the status line takes back what is no longer true. Engine 14.0.0, unchanged. Known issues gains three entries, and this is the part worth reading. Two engine defects were found in the same pass and are NOT fixed here, because the engine did not move: a join condition written ON right.x = left.y is refused outright, with the root cause named down to the line that pairs the keys by written order; and EXPLAIN gives the right input's child the wrong parent, so anything that draws the plan as a tree draws the wrong tree faithfully. The third entry is a gap in Studio itself - a routine in the tree can only be refreshed, though the engine has DROP FUNCTION and the catalogue already carries the body. Studio: 1030 green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Found the day 3.1.0 shipped, by using it. Engine 14.0.0, unchanged - nothing on NuGet moves.
What is corrected
DoubleTappedtravelsBubblealone, and a handler asked for its tunnelling route is no handler (#222).Known issues - the part worth reading
Two engine defects were found in the same pass and are deliberately not fixed here, because the engine did not move. Both are written up with their reproduction and root cause in Docs/KnownIssues.md:
ON right.x = left.yfails withColumn 'x' not found; in a chain, "the left input" is everything joined so far. Root cause named to the line -OptimizerJoinCondition.TryExtractEquiJoinKeypairs the keys by written order and never asks which input each column belongs to. Measured table of what works and what does not, plus the workaround.EXPLAINgives the right input's child the wrong parent. Anything drawing the plan as a tree draws the wrong tree faithfully - the renderer is not the defect.DROP FUNCTIONand the catalogue already carries the body.Studio: 1030 green.
🤖 Generated with Claude Code