In "after-pressing-SEND hindsight:" I suppose that for a system to really care about a leap second jump, it would have to be at least reasonably synched to the NIST clocks as a precondition -- otherwise the normal computer clock drift would mean that the clock is off by multiple seconds routinely. And if one is synched to NIST, then the leap second correction will cause your computer's clock to jump right on schedule, and you'd need to account for this in any precise time-measuring applications running in the dead of night, unless some very special software lets you delay your implementation of the leap second.
At any rate, SqLite shouldn't be dealing with any of that, right? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
