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

Inconsistent date v. datetime timestamp values #43

Open
cecilia-donnelly opened this issue Mar 22, 2016 · 0 comments
Open

Inconsistent date v. datetime timestamp values #43

cecilia-donnelly opened this issue Mar 22, 2016 · 0 comments

Comments

@cecilia-donnelly
Copy link
Contributor

A user reports:

One other issue that I’m noticing - when I send a new client record, the response from the web server shows the timestamp values with hours, minutes, seconds, and fractional seconds. However, when I fetch that same record back from the web service on a subsequent sync, the timestamp value is set to midnight UTC time.

I understand that we’re not currently storing time values, and that’s OK with MirrorSync, but it is important that the values returned during an insert operation are consistent with the values that we later read from the database, so you can either 1) return the values as midnight UTC time on the insert, or 2) retain the time portion when we later read from the database.

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

1 participant