-
-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[no-release-notes] GMS bump #4968
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mostly LGTM one comment
// same for d functions | ||
if _, ok := expr.(*dfunctions.HashOf); ok { | ||
return nil, ErrInvalidNonLiteralArgument.New(ds.Name(), expr.String()) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason d functions shouldn't just implement sql.FunctionExpression
?
@@ -111,27 +110,19 @@ func TestSingleScript(t *testing.T) { | |||
t.Skip() | |||
var scripts = []queries.ScriptTest{ | |||
{ | |||
Name: "trigger before update, with indexed update", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit git checkout main -- go/libraries/doltcore/sqle/enginetest/dolt_engine_test.go
We don't support UnresolvedFunctions as dolt table arguments, but those functions are fuly resolved when running them prepared, so additional logic is needed to skip them.