News for hackers. Stuff that matters.

A comment on Nanosecond timestamp collisions are common. Parent comment

Re:Nanosecond timestamp collisions are common by Timon3 on Friday July 21, 2023 @10:50AM (#36814486)
Why? Tight coupling doesn't make things easier.
[ Parent | on HN ]
Re:Nanosecond timestamp collisions are common by EGreg on Friday July 21, 2023 @11:59AM (#36815407)
You’re complaining that the infrastructure details are bleeding into the intrastructure implementation?
[ Parent | on HN ]
Re:Nanosecond timestamp collisions are common by Timon3 on Friday July 21, 2023 @12:02PM (#36815448)
Infrastructure details are bleeding into non-infrastructure implementation. Your database content is not an infrastructure implementation.
[ Parent | on HN ]
Re:Nanosecond timestamp collisions are common by EGreg on Friday July 21, 2023 @05:49PM (#36820352)
the content is not, but it can use a database function, such as CURRENT_TIMESTAMP or RANDOM() can it not?
[ Parent | on HN ]
Re:Nanosecond timestamp collisions are common by Timon3 on Saturday July 22, 2023 @02:46AM (#36823918)
I'm not sure what you're getting at. How are those connected to the topic? Those functions aren't infrastructure implementations either.
[ Parent | on HN ]