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

feat: Support scenarios where split-table and non-table split tenants… #155

Closed
wants to merge 1 commit into from

Conversation

geekeryy
Copy link

@geekeryy geekeryy commented Mar 20, 2024

… exist simultaneously in multi-tenant situations

Support scenarios where split-table and non-table split tenants exist simultaneously in multi-tenant situations

  • Do only one thing
  • Non breaking API changes
  • Tested

What did this pull request do?

User Case Description

… exist simultaneously in multi-tenant situations

Support scenarios where split-table and non-table split tenants exist simultaneously in multi-tenant situations
@geekeryy
Copy link
Author

@huacnlee Can you help me, thanks?

@@ -116,6 +116,10 @@ func (m ShardingMigrator) splitShardingDsts(dsts ...any) (shardingDsts []shardin
}

for _, suffix := range suffixs {
if len(suffix) == 0 {
Copy link
Collaborator

@huacnlee huacnlee Mar 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这里用 len(suffix) 能达到你的目的,但逻辑很奇怪。我们不能直接这样做

@geekeryy geekeryy closed this Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants