[GH-ISSUE #29] Include Seconds information in the sent_timestamp field #23

New issue

Closed

opened 2026-02-28 01:22:48 +03:00 by kerem · 6 comments

kerem commented

2026-02-28 01:22:48 +03:00

Owner

Originally created by @mrgkumar on GitHub (Aug 14, 2012).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/29

Currently the "sent_timestamp" does not include the seconds field in it. Could you please include that feature ?

Originally created by @mrgkumar on GitHub (Aug 14, 2012). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/29 Currently the "sent_timestamp" does not include the seconds field in it. Could you please include that feature ?

kerem closed this issue

2026-02-28 01:22:48 +03:00

kerem commented

2026-02-28 01:22:49 +03:00

Author

Owner

@ghost commented on GitHub (Aug 22, 2012):

Also, full year. ISO 8601 would be most preferable, because it is standard, unambiguously human readable, lexicographical order is the same as temporal order and is in general most machine-friendly of non-integer timestamp formats(for example, goes into database datetime columns as is.)

And by ISO 8601 I naturally mean combined extended date with extended time, with ' ' as the delimiter instead of T for increased human readability, with little to no decrease in machine compatibility. I.e. "YYYY-MM-DD HH:MM:SS"

@ghost commented on GitHub (Aug 22, 2012): Also, full year. ISO 8601 would be most preferable, because it is standard, unambiguously human readable, lexicographical order is the same as temporal order and is in general most machine-friendly of non-integer timestamp formats(for example, goes into database datetime columns as is.) And by ISO 8601 I naturally mean combined extended date with extended time, with ' ' as the delimiter instead of T for increased human readability, with little to no decrease in machine compatibility. I.e. "YYYY-MM-DD HH:MM:SS"

kerem commented

2026-02-28 01:22:49 +03:00

Author

Owner

@eyedol commented on GitHub (Aug 22, 2012):

@agenttihirvinen Thanks for the mention of ISO 8601. I will look into this more.

@eyedol commented on GitHub (Aug 22, 2012): @agenttihirvinen Thanks for the mention of ISO 8601. I will look into this more.

kerem commented

2026-02-28 01:22:49 +03:00

Author

Owner

@eyedol commented on GitHub (Aug 26, 2012):

sent_timestamp is now the raw timestamp value. No pre-formatting. This is to allow the client to take care of the formatting. I'm closing this issue

@eyedol commented on GitHub (Aug 26, 2012): sent_timestamp is now the raw timestamp value. No pre-formatting. This is to allow the client to take care of the formatting. I'm closing this issue

kerem commented

2026-02-28 01:22:49 +03:00

Author

Owner

@ghost commented on GitHub (Aug 27, 2012):

Raw meaning a UNIX timestamp? That is satisfactory as well.

@ghost commented on GitHub (Aug 27, 2012): Raw meaning a UNIX timestamp? That is satisfactory as well.

kerem commented

2026-02-28 01:22:49 +03:00

Author

Owner

@mrgkumar commented on GitHub (Aug 27, 2012):