Skip to content

Conversation

@Indy2222
Copy link

This fixes the following error:

ValueError: time data '2021-02-21T10:14:42.879Z' does not match format '%Y-%m-%dT%H:%M:%SZ'

This fixes the following error:

ValueError: time data '2021-02-21T10:14:42.879Z' does not match format '%Y-%m-%dT%H:%M:%SZ'
@ghost ghost added Tables customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Feb 21, 2021
@ghost
Copy link

ghost commented Feb 21, 2021

Thank you for your contribution Indy2222! We will review the pull request and get back to you soon.

@seankane-msft
Copy link
Contributor

@Indy2222 I created a new PR that supports milliseconds on datetime on both serialization and deserialization, let me know what you think of it. In addition, we're working on custom deserialization support and hope to have it included in the next release. Thank you for reporting the issue!

@Indy2222
Copy link
Author

@Indy2222 I created a new PR that supports milliseconds on datetime on both serialization and deserialization, let me know what you think of it. In addition, we're working on custom deserialization support and hope to have it included in the next release. Thank you for reporting the issue!

Your solutions looks better than mine as it does not toss away the additional precision and works pretty much with any number of decimal places.

When will be the next beta with this fix released?

@seankane-msft
Copy link
Contributor

@Indy2222 our next release will go out the second week of March, most likely on 3/9.

@Indy2222 Indy2222 deleted the feature/fix-tables-date-parsing branch February 26, 2021 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

customer-reported Issues that are reported by GitHub users external to the Azure organization. Tables

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants