Open
Conversation
- Replace ALTER COLUMN SET DEFAULT with MODIFY COLUMN in v1.7 migration (TiDB does not support ALTER COLUMN SET DEFAULT syntax) - Add TiDB >= 7.2 requirement note on CHECK constraints in nexus_endpoints_partition_status table
- Add TiDB v7.5.7 and v8.5.5 to CI test matrix using mysql8 driver with extra_env overrides for MYSQL_SEEDS/MYSQL_PORT - Add TiDB services to dev and CI docker-compose files - Add TiDB config (allow-expression-index) and init SQL (temporal user + tidb_enable_noop_functions) - Add SKIP_VISIBILITY_SCHEMA env var to skip loading visibility schema on TiDB (lacks FULLTEXT and multi-valued indexes) - Add develop/tidb-test.sh and develop/mysql-test.sh for local testing - Add docs/TIDB_COMPATIBILITY.md documenting all findings
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
TiDB Compatibility as a Mysql backend
Why?
To support a more scalable sql backend.
How did you test it?
Potential risks
Any change is risky. Identify all risks you are aware of. If none, remove this section.