Allow distinct types in schema::custom()
#2326
Merged
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.
PR Info
schema::custom()
requirescol
andname
to be of same type #2325Bug Fixes
col
andname
to come from differentDeriveIden
structs inschema::custom()
.Breaking Changes
schema::custom()
gains another generic type argument.Strictly speaking, this may be considered a breaking change. However, it remains unclear whether explicitly stating the generic type argument is something that is actually done in the wild.
Rationale
The proposed change is in line with the existing signature of
schema::enumeration()
, another method that uses more than oneIntoIden
argument:sea-orm/sea-orm-migration/src/schema.rs
Lines 549 to 560 in aa0bbd9