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.

Sign up for GitHub

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

Jump to bottom

Missing microseconds when using TCP API #29

Open
enumag opened this issue Feb 14, 2019 · 0 comments
Open

Missing microseconds when using TCP API #29

enumag opened this issue Feb 14, 2019 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@enumag
Copy link

enumag commented Feb 14, 2019

When using TCP API I get for example this time: 1550161376571 which corresponds to 2019-02-14T16:22:56.571000+00:00. The 1550161376 is apparently a UNIX timestamp while 571 is the number of milliseconds. I'd like to have microseconds as well. HTTP API does return microseconds so there is no reason for TCP API to not return them.
@oskardudycz oskardudycz transferred this issue from EventStore/EventStore Dec 15, 2021
@oskardudycz oskardudycz added enhancement New feature or request good first issue Good for newcomers labels Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@enumag @oskardudycz