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
planner: support universal SQL bindings #48875
Labels
epic/sql-plan-management
sig/planner
SIG: Planner
type/feature-request
This is a feature requests on the product
Comments
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
AilinKid
pushed a commit
to AilinKid/tidb
that referenced
this issue
Jan 17, 2024
AilinKid
pushed a commit
to AilinKid/tidb
that referenced
this issue
Jan 17, 2024
…inding for plan cache (pingcap#50133) ref pingcap#48875
AilinKid
pushed a commit
to AilinKid/tidb
that referenced
this issue
Jan 17, 2024
13 tasks
This was referenced Jan 24, 2024
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
epic/sql-plan-management
sig/planner
SIG: Planner
type/feature-request
This is a feature requests on the product
Feature Request
Is your feature request related to a problem? Please describe:
In the context of database consolidation, it is common to encounter situations where identical applications repeat on multiple database schemas. When addressing performance issues with SQL binding, it becomes imperative to replicate the SQL bindings across each of these schemas. In some practical scenarios, it is not unusual to have approximately 500 databases within a single cluster. Implementing SQL binding across all these schemas can pose significant challenges for customers.
Describe the feature you'd like:
Support the syntax like:
The user can use wildcards as DB names when creating bindings.
The text was updated successfully, but these errors were encountered: