Rican7
Joined 13 years ago
Joined 13 years ago
huh? It's only been about 9
The newer draft proposal allows for multiple different options of time information to be added to a UUIDv7 encoding, beyond the typical 48-bits of Unix epoch millisecond data.
https://datatracker.ietf.org/doc/html/draft-ietf-uuidrev-rfc...
They literally just launched (in preview) a settings GUI: https://github.com/microsoft/terminal/releases/tag/v1.6.1027...
Unfortunately, though, its a bit complex to even try to use the local dictionary: https://github.com/Rican7/define/issues/1
I appreciate you taking the time to look at the source. I used this, like I do most of my side projects, as an opportunity to learn a few things.
I wanted a generic abstraction so that multiple sources could be used. Originally I didn't want or think of the need to support multiple sources, but it quickly became apparent how necessary that was when looking at the quality of free vs paid vs personal-key-required sources.
In any case, thanks for checking it out!
This is what CloudBleed looks like, in the wild: https://gfycat.com/ElatedJoyousDanishswedishfarmdog
A random HTTP request's data and other data injected into an HTTP response from Cloudflare.
Sick.
> PostgreSQL 17 supports using identity columns and exclusion constraints on partitioned tables.
> PostgreSQL 17 also includes a built-in, platform independent, immutable collation provider that's guaranteed to be immutable and provides similar sorting semantics to the C collation except with UTF-8 encoding rather than SQL_ASCII. Using this new collation provider guarantees that your text-based queries will return the same sorted results regardless of where you run PostgreSQL.