DuckDB Server driver #25
Merged
Conversation
This file contains 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
* docs: Pricing update * Edits * Renamings
…#8813) Bumps [next](https://github.com/vercel/next.js) from 13.5.6 to 14.2.10. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v13.5.6...v14.2.10) --- updated-dependencies: - dependency-name: next dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Add a link to Atlas BI Connector deprecation * Fix join relationships. Closes cube-js#8758 * Add an example of multiple primary keys
* ci: Bump actions/setup-python to v5 * ci: Bump actions/github-script to v7 * ci: Bump docker/build-push-action action to v6
cube-js#8884) Also remove duplicated test_wrapper_limit_zero This case is already covered with compile::test::test_wrapper::test_wrapper_limit_zero
…-js#8921) * fix: ignore Data Access Policy-defined visibility in dev-mode and playground * fix: patch isVisible when applying member level policies
…ault in convertTzForRawTimeDimension flag (cube-js#8931)
…s empty (cube-js#8883) Without these checks TableScan->CubeScan rule is, technically, unsound. For now it's just a sanity check, initial planning should not generate TableScan with any of that.
…e-js#8945) Motivation for change: While working on the new layer for MDX, I discovered that all members in views are defined as View's members. This leads to a problem: I am not able to separate them by cubes to align our model with Analysis Services.
sqlstring uses different question mark sequences for different placehloders: ? for value, ?? for identifier, and skips replacing for ???
Flatten aggregation of WrappedSelect with filters. Some queries in tests reduced to a single CubeScan with member expressions, so tests have changed Also a bunch of supporting changes: * Tighten rule for non-trivial wrapper pullup * Make var_iter and var_list_iter more hygienic * Rename ungrouped field of WrappedSelectNode, WrapperPushdownReplacer and WrapperPullupReplacer to push_to_cube This name seems more appropriate, because actual WrappedSelect can represent grouped query when this field is set to true * Avoid mixing flags from pushdown and pullup replacers * Add member_to_alias and format TestConnectionTransport SQL output
…PARAMS are used inside dimensions/measures (cube-js#8867) * fix(schema-compiler): fix Maximum call stack size exceeded if FILTER_PARAMS are used inside dimensions/measures * add tests * move guard to the filter_params proxy
cube-js#8950) Fixes: cube-js#8949 --------- Co-authored-by: Dmitry Patsura <zaets28rus@gmail.com>
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.
No description provided.