Skip to content
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

Call for participation: fix TiDB behaviors for incompatible statements #598

Closed
11 tasks done
tangenta opened this issue Oct 31, 2019 · 3 comments
Closed
11 tasks done
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@tangenta
Copy link
Contributor

tangenta commented Oct 31, 2019

The event on improving parser compatibility has been well attended by a lot of contributors, and most of the compatibility issues have been solved.

However, there are statements that are supported syntactically by parser but not functionally by TiDB. To avoid unexpected behaviors in TiDB, we have analyzed each type of statement to decide whether TiDB should throw an error, a warning, or just ignore it.

The final implementation work is assigned to the interested contributors.

Here are some issues:

@bb7133
Copy link
Member

bb7133 commented Jan 12, 2020

How about the TEMPORARY VIEW?

@kennytm
Copy link
Contributor

kennytm commented Jan 12, 2020

@bb7133 You could edit the description to add items.

@morgo
Copy link
Contributor

morgo commented Mar 9, 2021

How about the TEMPORARY VIEW?

MySQL doesn't support such a feature. It supports global scope or statement-scoped views (aka CTEs) but not session-scoped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants