forked from rust-postgres/rust-postgres
-
Notifications
You must be signed in to change notification settings - Fork 24
Merge upstream to pick up new fixes and features #32
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
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
The impl now directly computes `Timestamp` rather than going through `DateTime` and `Zoned`.
`Timestamp` already has impl and is semantically accurate for mapping to `timestamptz`, unlike `Zoned`. End users can do their own conversions from `Timestamp` to `Zoned` if desired.
This adds tests in the same fashion as the existing ones for `chrono` and `time`. Overflow is now handled using fallible operations. For example, `Span:microseconds` is replaced with `Span::try_microseconds`. Postgres infinity values are workiing as expected. All tests are passing.
The implementation was previously removed as per jiff author comment.
`test_date_time_params` and `test_with_special_date_time_params` could fail when run with a non-UTC system time zone. In Postgres, if no time zone is stated in the input string, then it is assumed to be in system time. This means that in these tests, a correctly parsed `DateTime<Utc>` could be compared to an incorrectly offset time. The offset component is now included in the test strings of these tests. This component is already present in the test strings for `time::OffsetDateTime`.
Fix `chrono::DateTime<Utc>` tests
Add Jiff support
add `load_balance_hosts` to `Debug` impl for `Config`
Getting `PrimitiveDateTime` panics if the value is infinity. This commit fixes the panic. An infinity test is added, mirroring the existing one for chrono.
…ni/jiff-no-default-features feat(postgres-types): disable default features of `jiff`
…n-closure Improve is_closed effectiveness
Co-authored-by: Tristan Partin <tristan@partin.io>
…ni/pg-18 chore: start testing with PostgreSQL 18
…ni/futures-util-no-default-features feat: disable default features of `futures-util` for `postgres`
Types implementing the Error trait should print some inner Error **xor** return that inner Error from its Error::source impl. Otherwise, the same error will be printed multiple times when printing an Error's entire source chain, which is unhelpful.
fix an Error/Display impl
…ni/check_connection-doc-comment Improve `check_connection` doc comment
Expose simple query raw method in tokio postgres
Add method `raw_size_bytes` to `Row`
Implement FromSql for Box<T: FromSql> and ToSql for Box<T: ToSql>
chore: reflect with-jiff-0_2 feature in docs
Signed-off-by: Petros Angelatos <petrosagg@gmail.com>
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.
No description provided.