-
Notifications
You must be signed in to change notification settings - Fork 22
Fix BigQuery outer-wrap ORDER BY and dataset-scoped introspection #313
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
Merged
whimo
merged 2 commits into
main
from
artemy/fix-bigquery-outer-order-and-introspection
Aug 19, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
Repository: MotleyAI/slayer
Length of output: 50372
🏁 Script executed:
Repository: MotleyAI/slayer
Length of output: 24997
🌐 Web query:
BigQuery INFORMATION_SCHEMA COLUMNS project dataset qualifier syntax project.dataset.INFORMATION_SCHEMA.COLUMNS💡 Result:
To query the BigQuery INFORMATION_SCHEMA.COLUMNS view, you must use either a dataset qualifier or a region qualifier [1][2]. The syntax for these qualifiers, including the optional project ID, is as follows: 1. Dataset Qualifier Syntax The dataset qualifier restricts results to a specific dataset. Use this format:
[PROJECT_ID.]DATASET_ID.INFORMATION_SCHEMA.COLUMNS[1][3] If you omit the PROJECT_ID, BigQuery defaults to the project in which the query is executing [2][4]. 2. Region Qualifier Syntax The region qualifier restricts results to a specific region within a project. Use this format:[PROJECT_ID.]region-REGION.INFORMATION_SCHEMA.COLUMNS[1][3] Key Considerations: - Project Qualifier: You can prepend the optional PROJECT_ID to both dataset and region qualifiers to query data across different projects [2][4]. - Permissions: When using a dataset qualifier, you need appropriate permissions for the dataset [1][3]. When using a region qualifier, you need permissions for the project [1][3]. - Location Matching: Queries against INFORMATION_SCHEMA views must match the location of the dataset or the regional qualifier used; otherwise, the query will fail [5]. Example: To query columns in a specific dataset across another project, use:SELECT * FROMmy-project.my_dataset.INFORMATION_SCHEMA.COLUMNS;[1][6]Citations:
🏁 Script executed:
Repository: MotleyAI/slayer
Length of output: 20979
Handle unsupported BigQuery name shapes explicitly.
BigQuery requires a dataset or region-qualified
INFORMATION_SCHEMA.COLUMNSview. This code leaves bare names unqualified and treatsproject.dataset.tableas the single dataset identifierproject.dataset.Reject unsupported shapes early, or quote project and dataset components separately. Add tests for bare, dataset-qualified, and project-qualified names.
🤖 Prompt for AI Agents
Source: MCP tools