Skip to content
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

Date/time string format expensive to parse. #19

Open
remcovanschadewijk opened this issue Jan 13, 2021 · 0 comments
Open

Date/time string format expensive to parse. #19

remcovanschadewijk opened this issue Jan 13, 2021 · 0 comments
Assignees

Comments

@remcovanschadewijk
Copy link

In the exported CSV table, the date/time strings are quite verbose. For example: Wed Feb 15 2017 07:54:22 GMT+0100 (Central European Standard Time)

This string format is computationally expensive to parse. Could the format be changed to ISO 8601 compliant strings? The trade-off may be reduced human readability, but I suspect the CSV tables would be parsed in some way anyway.

Second, exporting date/time as UTC would make sense, as the recorded data refers to worldwide user interactions. It also simplifies parsing since it can then be treated as time zone naive.

@mvallet91 mvallet91 self-assigned this Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants