Who isn't posting on here today?

[Moscow Mule]

What happens when the clicky thing goes off-line and you lose track of your clicks?

Multiple clicky things. Need more than 2 though, otherwise you end up with a duality drive...

[TimberWolf]

I dunno, it's all drag 'n' drop, 'innit?

You mean use something the O/S provide like timeinMillisecondsSince1970? That would still be date/time dependent though and go screwy when the clocks change? A pure clicky thing that didn't reference data/time would be handy, though if it were independent of data and time conversion to a date/time might be impossible.

[TimberWolf]

Multiple clicky things. Need more than 2 though, otherwise you end up with a duality drive...

A man with two watches never knows the right time.

[Moscow Mule]

A man with two watches never knows the right time.

No, but he has got the makings of an excellent duality drive. Just ask threaded.

[OwlHoot]

Makes sense, but where do you get the "clicks since a fixed epoch" from?

man time(2)

well until 2037 if you use a 32-bit counter.

You'd be amazed how many permie bozo database "designers" store datetime values in local time, instead of Zulu time or epoch time a-la Dim Prawn, because "we don't have to worry about different time zones".

[TimberWolf]

man time(2)

well until 2037 if you use a 32-bit counter.

You'd be amazed how many permie bozo database "designers" store datetime values in local time, instead of Zulu time or epoch time a-la Dim Prawn, because "we don't have to worry about different time zones".

Ah, no summer time savings to worry about there then, it presumably does the conversion to local time as necessary. That algorithm is going to need updating if we convert to GMT+1 though, or whatever the government proposal is.

Though on reflection, a transaction count would probably serve adequately as a clicky thing in most cases.