> and to make DB indices happy. You can do both, use a low precision timestamp with overflows in the ID to keep the index happy, and add a proper timestamp fie

> and to make DB indices happy. You can do both, use a low precision timestamp with overflows in the ID to keep the index happy, and add a proper timestamp field for analytics. The 32 + 96 split is what postgres uses for example. I'd say that's a pretty good endorsement.