-
Notifications
You must be signed in to change notification settings - Fork 13
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
[pg] SET statement failed #193
Labels
Comments
VWagen1989
added
bug
Something isn't working
compatibility
Be compatible with some old fashion request
labels
Nov 21, 2024
VWagen1989
added a commit
that referenced
this issue
Nov 25, 2024
VWagen1989
added a commit
that referenced
this issue
Nov 27, 2024
VWagen1989
added a commit
that referenced
this issue
Nov 27, 2024
VWagen1989
added a commit
that referenced
this issue
Nov 28, 2024
VWagen1989
added a commit
that referenced
this issue
Nov 28, 2024
VWagen1989
added a commit
that referenced
this issue
Nov 29, 2024
* feat(pg): supports SET/SHOW statement (#193) * fix: bypass the configuration of DuckDB setting to backend DuckDB connection * fix: solve problems of getting and setting session variables * fix: solve problems of unit test in binlogreplication * fix: RESET ALL is not supported yet * refactor: move handlers for pg_catalog to a new file * fix: adopt CR feedback
Done in #226 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Maybe we should store all the system variables as the MySQL part does.
The text was updated successfully, but these errors were encountered: