Viewing profile — sergeyprokhoren

[dead]

The PostgreSQL uuidv7() developers are leaning toward a different approach to solving timestamp leaks, similar to FHSS ( https://en.wikipedia.org/wiki/Frequency-hopping_spread_spec…

PostgreSQL Gains a Built-in UUIDv7 Generation Function for Primary Keys (many interesting details) https://habr.com/en/news/950340/

Offsetting the timestamp is much better. Use the uuidv7(INTERVAL shift) function in PostgreSQL 18 https://www.postgresql.org/docs/18/functions-uuid.html in Percona Server for MySQL…

95% of the comments here have nothing to do with reality. What May Surprise You About UUIDv7 https://medium.com/@sergeyprokhorenko777/what-may-surprise-y...

If you shift the timestamp forward by 5 thousand years, it can hardly be called just a decrease in precision.

Bad idea. In PostgreSQL 18 the optional parameter shift will shift the computed timestamp by the given interval https://www.postgresql.org/docs/18/functions-uuid.html

https://biggo.com/news/202509050143_6NF_File_Format_Debate

What does looks "old school" mean? Do you want to wrap this format in JSON like JSON-LD? I don't mind

See "DSL for Bitemporal Sixth Normal Form with UUIDv7" https://github.com/sergeyprokhorenko/6NF_DSL

This is a fairly common problem. Data is often transferred between information systems in denormalized form (tables with hundreds of columns - attributes). In the data warehouse, t…

[dead]

[dead]