MySQL 顺序Guid算法更新 #258
Closed
MySQL 顺序Guid算法更新 #258
Conversation
This file contains 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
|
Why use this over the existing SequentialGuidValueGenerator.cs in upstream? |
|
This article can explain that why the existing SequentialGuidValueGenerator.cs in upstream doesnot work correctly in MySQL https://www.codeproject.com/articles/388157/guids-as-fast-primary-keys-under-multiple-database |
|
Ok, makes sense if SQL Server is putting their sequential values at the end. MySql needs them at the beginning. Let me see if I can fix this up a little, add tests, and open a separate PR. |
|
thank you |
|
We'll need to take into account GUID format in MySqlScopedTypeMapper.cs It could be either |
Merged
|
Closing in favor of #260 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
不同数据库顺序guid要求不同