Time zones

[djbur...@gmail.com]

Hi all,

I believe I've found a "feature" in Fosstrak. Not quite yet prepared to stick my neck out & call it a bug, but I could do with some clarification:-)

I've got a transaction event that looks like e.g.:
<TransactionEvent>
  <eventTime>2014-07-13T22:12:13+00:00</eventTime>
  <eventTimeZoneOffset>+00:00</eventTimeZoneOffset>
  [...]
<TransactionEvent>

Note that I'm (deliberately) using GMT, as my RFID readers are set up to ignore any summertime changes.

In Fosstrak, this turns into a set of records such as:
# id, eventTime, eventTimeMs, recordTime, recordTimeMs, eventTimeZoneOffset, parentID, action, bizStep, disposition, readPoint, bizLocation
'655754', '2014-07-13 23:12:13', '1405289533000', '2015-10-28 19:50:24', '1446061823523', '+00:00', NULL, 'ADD', '1', '1', '11', '9'

Note that the eventTimeZoneOffset is still +00:00, but my time now has an hour added onto it!

I imagine there is a setting somewhere in MySQL or Apache or Fosstrak or somewhere that's telling the capture client to turn everything into system time (i.e. BST for events in July 2014), and the capture client doesn't have the necessary code to be able to ignore the setting and believe the data it's being sent!

I think my workaround here will have to be to turn everything into summertime before submitting:-(

Regards,
Dave

[Dave Burbridge]

Of course-i should also check what the epcis-query output is for that transaction.I'll do that when I have time,but I think there's still a problem.
D

> --
> You received this message because you are subscribed to a topic in the Google Groups "fosstrak" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/fosstrak/JfZby3PQhT8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to fosstrak+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

[djbur...@gmail.com]

OK, I've now checked the actual SOAP response. Interestingly, it comes out as:
               <TransactionEvent>
                  <eventTime>2014-07-13T23:12:13.000+01:00</eventTime>

                  <eventTimeZoneOffset>+00:00</eventTimeZoneOffset>
                  [...]

               </TransactionEvent>

Which I think is sort of correct.
eventTime itself does indeed reflect the original input (23:12+01:00 == 22:12+00.00).
But is the eventTimeZoneOffset the offset for the zone in which the event "took place", i.e. in this case, in GMT since that's what I originally recorded with my RFID reader?

Unfortunately, this behaviour is playing havoc with my attempts to delete a range of data in EPCIS and reprocess/reload it for test purposes:-) I think I need to look at the SQL I'm using for the "delete from" query instead...

Regards,
Dave