Conversation
#[postgres(schema = ...)] can be used to make it so the type only accepts types with the matching schema name. if the attribute is omitted, any schema is allowed (same as before). fixes rust-postgres#627
purple-ic
marked this pull request as draft
April 18, 2026 03:13
Author
|
actually hold on: i guess i could make the schemas use a |
Author
|
ah, nevermind, you can't create your own |
purple-ic
marked this pull request as ready for review
April 18, 2026 03:17
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.
#[postgres(schema = ...)]can be used to make it so the type only accepts types with the matching schema name. if the attribute is omitted, any schema is allowed (same as before).unfortunately this adds tests that create non-temporary types (because we use our own schemas, and afaik temporary things are only possible under
pg_temp_*schemas). the tests fail if you runcargo testtwice with the same database (though it seems there were already a few tests with this issue). lmk if there's a fix.also for whatever reason the
postgres::test::is_closedtest fails on my machine? i can only assume this is a bug with the test suite or some issue with my setup, because i touched absolutely nothing that would affect that...fixes #627