Select Code to Download

According to your code, it seems that you are interested only in two r
+ecords next to one another. I draw this conclusion because if you hav
+e three records on the same channel and ID, you'll not be able to tel
+l if, for example, the third one and the first one are more than an h
+our apart. Is that really what you want? The only scenario that immed
+iately explains to me the session code you're using is a periodic tas
+k completion, like traveling a circular route and crossing a start/fi
+nish line or passing a token back and forth on a network.

<b>quote</b>
I might just need more info to understand this, but there seems to be 
+issues with the logging method. There's no indication in the informat
+ion you present as to what's a start record and what's a stop record,
+ yet you consider any pair of matching IDs with no likewise matching 
+IDs between them a "record". Yet if you have more than two, you'll be
+ considering the first and second as a session record, the second and
+ the third as a session record, and the third and the fourth... Unles
+s you're absolutely sure you'll never have more than two lines with t
+he same ID (like if it's a unique session ID), then you're counting m
+ore sessions than you have. OTOH, if you're guaranteed to never have 
+more than two lines with the same ID, then why do you need a count of
+ the occurrences for that ID? Are you timing network connections, lap
+ times around a track, stops at physical tool booths on a highway, or
+ what?

select * from records
where tids = ( xxxxxxxx,xxxxxx,xxxxxx ... ) # <--- read from TIDS file
and channel = seven
and time > 3600