feat(apalis-sql): add optional time crate support #654
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
Remove chrono dependency from apalis-sql and introduce a generic SqlTimestamp trait. This allows downstream crates (apalis-postgres, apalis-mysql, apalis-sqlite) to choose their own datetime library (chrono or time) without apalis-sql being opinionated. TaskRow is now generic over T: SqlTimestamp, enabling each SQL backend to use its preferred datetime type.
This was referenced Dec 25, 2025
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.
Summary
SqlTimestamptrait for datetime abstractiontimecrate support alongside defaultchronoRef: #649