-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
sql: add support for the ALTER SCHEMA RENAME TO
command
#50880
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Comments
12 tasks
rohany
added a commit
to rohany/cockroach
that referenced
this issue
Aug 3, 2020
Touches cockroachdb#50880. Touches cockroachdb#50884. This commit adds the boilerplate for adding the `ALTER SCHEMA` and `DROP SCHEMA` statements. Release note: None
craig bot
pushed a commit
that referenced
this issue
Aug 3, 2020
52167: sql: parse and recognize `ALTER SCHEMA` and `DROP SCHEMA` r=otan a=rohany Touches #50880. Touches #50884. This commit adds the boilerplate for adding the `ALTER SCHEMA` and `DROP SCHEMA` statements. Release note: None 52232: sql: don't show grouping columns as aggregations in EXPLAIN r=RaduBerinde a=RaduBerinde EXPLAIN shows grouping columns as aggregations. This was carried over from the heuristic planner. Now the groupNode always produces all grouping columns; we don't need to list them as aggregations. Release note (sql change): EXPLAIN no longer shows grouping columns as "aggregations" for the group operator. Co-authored-by: Rohan Yadav <[email protected]> Co-authored-by: Radu Berinde <[email protected]>
rohany
added a commit
to rohany/cockroach
that referenced
this issue
Aug 6, 2020
Fixes cockroachdb#50880. This commit implements the `ALTER SCHEMA RENAME TO` command. It reuses the existing schema change infrastructure to handle a more general case of an arbitrary descriptor that just needs names and existing leases drained. Release note (sql change): Implement the `ALTER SCHEMA RENAME TO` command.
rohany
added a commit
to rohany/cockroach
that referenced
this issue
Aug 10, 2020
Fixes cockroachdb#50880. This commit implements the `ALTER SCHEMA RENAME TO` command. It reuses the existing schema change infrastructure to handle a more general case of an arbitrary descriptor that just needs names and existing leases drained. Release note (sql change): Implement the `ALTER SCHEMA RENAME TO` command.
rohany
added a commit
to rohany/cockroach
that referenced
this issue
Aug 12, 2020
Fixes cockroachdb#50880. This commit implements the `ALTER SCHEMA RENAME TO` command. It reuses the existing schema change infrastructure to handle a more general case of an arbitrary descriptor that just needs names and existing leases drained. Release note (sql change): Implement the `ALTER SCHEMA RENAME TO` command.
craig bot
pushed a commit
that referenced
this issue
Aug 13, 2020
52313: colexec: add default comparison operator r=yuzefovich a=yuzefovich Depends on #52315. **colexec: add default comparison operators** This commit introduces default comparison projection and selection operators that handle all `tree.ComparisonExpr`s for which we don't have optimized implementations. The main operators are very similar to `defaultBuiltinFuncOperator`, but we also introduce optimized adapter implementations from `tree.ComparisonExpr` to a vectorized friendly model. Quick benchmarks show about 3.5x improvement in speed of `IS DISTINCT FROM` projection operator against the wrapped post-processing spec. Addresses: #49781. Release note (sql change): Vectorized execution engine now fully supports comparison operators (things like `ILIKE`, `IS NOT DISTINCT FROM`, `SIMILAR TO`, and several others). **colexec: add support for Tuple expressions and clean up tests** This commit adds support for `tree.Tuple` expressions which are supported either by pre-evaluation during planning (and handling the result as other constant values) if the tuple is constant or by planning projection operators for each expression in the tuple and then using newly-introduced `tupleProjOp` if the tuple expression is not constant. The support required refactoring of IsNull* operators to template out special "is tuple null" variants (because tuple have very peculiar null-handling semantics). It also required that we fallback to the default comparison operators on things that we have optimized support for (for example, EQ), also because of the null-handling semantics. It also improves the tests to handle datum-backed types better. Note that a single unit test in `aggregators_test.go` has been switched to use `types.TimeTZ` instead of `types.Jsonb` because of the differences in order of `string`s and `json.JSON.String()` (the former is the "expected" value whereas the latter is the actual; it was simpler to switch the test to use a different datum-backed type). Release note: None 52349: sql: implement `ALTER SCHEMA RENAME TO` r=rohany a=rohany Fixes #50880. This commit implements the `ALTER SCHEMA RENAME TO` command. It reuses the existing schema change infrastructure to handle a more general case of an arbitrary descriptor that just needs names and existing leases drained. Release note (sql change): Implement the `ALTER SCHEMA RENAME TO` command. Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Rohan Yadav <[email protected]>
rohany
added a commit
to rohany/cockroach
that referenced
this issue
Aug 13, 2020
Fixes cockroachdb#50880. This commit implements the `ALTER SCHEMA RENAME TO` command. It reuses the existing schema change infrastructure to handle a more general case of an arbitrary descriptor that just needs names and existing leases drained. Release note (sql change): Implement the `ALTER SCHEMA RENAME TO` command.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
This command renames a schema.
The text was updated successfully, but these errors were encountered: