Skip to content

Documentation for temporary tables #702

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.

Sign up for GitHub

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
systay merged 13 commits into from
Feb 17, 2021
Merged

Documentation for temporary tables #702

Changes from 2 commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
dde6a14
documentation for temporary tables
harshit-gangal Feb 9, 2021
7a0cfd5
addressed review comments
harshit-gangal Feb 11, 2021
882805f
more info about reserved connections
systay Feb 17, 2021
1b7fcc8
shutting down reserved connections
systay Feb 17, 2021
2e0f702
shutting down reserved connections
systay Feb 17, 2021
d1be3d6
shutting down reserved connections
systay Feb 17, 2021
c16dccd
info about advisory locking
systay Feb 17, 2021
384f85f
spelling
systay Feb 17, 2021
6f8f08d
temp tables
systay Feb 17, 2021
a91f20a
typo
systay Feb 17, 2021
01da73e
links
systay Feb 17, 2021
5a04610
links
systay Feb 17, 2021
73605f1
links
systay Feb 17, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion content/en/docs/reference/compatibility/mysql-compatibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,12 @@ To configure VTGate to support `TLS` set `-mysql_server_ssl_cert` and `-mysql_se

## Temporary Tables

Vitess does not support the use of temporary tables.
Vitess has limited support for temporary tables. It works only for unsharded keyspaces.

If the user creates a temporary table then the session will start using reserved connections for any query sent on that session.

The query plans generated by this session will not be cached. It will still continue to use the query plan cached from other non-temporary table sessions.


## Character Set and Collation

Expand Down