Add trait bound for binary PostgreSQL array #2503
Merged
Conversation
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
|
Anything that can be done to help move this forward? |
|
not much really, please come back if there are issues |
🎉 Released In 1.1.8 🎉Thank you everyone for the contribution! |
hjarraya
pushed a commit
to sambaclab/sea-orm
that referenced
this pull request
Apr 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
This adds a missing trait bound that allows
Vec<u8>to be stored in a PostgreSQL array.Bug Fixes
The CLI will currently happily generate an entity that contains a
Vec<Vec<u8>>when encountering abytea[]column in PostgreSQL. This entity will however fail to compile, as theTryGetabletrait bound is missing for this type.This PR adds the missing trait bound.