Fixed datetime encode bug #1
Open
Conversation
This file contains 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
…oded incorrectly for Parse
If there are related objects returned in the query, the default behaviour is to fetch and return them. If includeRelated is set to False, these included objects are not fully fetched.
|
@pktck I didn't check if this patch would chop off 3 digits from python datetime.datetime microseconds converting to Parse milliseconds, but for the rest your should definitely accept @alastairpat's patch. @alastairpat generally you shouldn't add irrelevant commits to your pull request. Cheers, |
amanahuja
pushed a commit
to amanahuja/ParsePy
that referenced
this pull request
Oct 31, 2012
Request to update README doc
nesteggs
pushed a commit
to nesteggs/ParsePy
that referenced
this pull request
Jan 4, 2013
geoPoints
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.
Fixed bug where if a datetime lacked milisecond precision, it was encoded incorrectly for Parse