Refresh SQLAlchemy object after creation in POST #647
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
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.
Partially fixes issue #630.
What change does this make? This adds
Sesson.refresh(obj)call to the SQLAlchemy object created during a POST request. Callingrefresh()after the object has been added and the session flushed causes any timezone-aware datetime attribute deserialized from the incoming request to be re-read from the database as timezone-naive datetime if the database is configured that way.How does this affect the user? This corrects a bug in which the response to a POST request incorrectly still showed the timezone-aware datetime attribute even though the database was storing only the timezone-naive datetime attribute.