Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So use timestamps with sub-second precision, which virtually every SQL database supports (even ones like SQLite that don't have built-in date/time types).


I don't think you know enough about how databases work to even try to be giving advice.

The timestamp generated in a transaction is generally the time the transaction started, which means it is always the same within the same transaction.


> I don't think you know enough about how databases work to even try to be giving advice.

That's both incorrect and entirely unwarranted.


Obviously sub-tasks will not typically be in the same transaction.


What about ntpd updates, or multiple scripts running in parallel?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: