Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

vitessio / vitess Public

Notifications You must be signed in to change notification settings
Fork 2.1k
Star 18.9k

Code
Issues 776
Pull requests 48
Actions
Projects 7
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Update the schema copy with minimal changes#8067

Merged

systay merged 4 commits intovitessio:mastervitessio/vitess:masterfrom planetscale:schema-fetchplanetscale/vitess:schema-fetchCopy head branch name to clipboard

May 11, 2021

+62-17

Conversation Commits4 (4)Checks Files changed

Commits

Commits on May 7, 2021

how to update the schemacopy with minimal changes to it
systay
committed
copy schema state more carefully
systay
committed

Commits on May 10, 2021

use IN instead of ORing together a bunch of equality comparisons
systay
committed
Use Stream instead of Exec to not have maxrows
systay
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.