[yepyoukno]

Perils of “UUIDv4”. Everyone knows that’s what UUIDv7 was really for, and you should always convert that to binary to optimize everything.

[themafia]

> and you should always convert that to binary to optimize everything

I disagree. I tried this once. Now you need a client access layer to touch the DB in any context. All your console tools no longer work well or at all. If they show up in URLs you need to deoptimize them for transport.

You give up a lot of convenience for this optimization. You should be absolutely sure your design requires it before using it.

[JSR_FDED]

Small nit: uuid7 is 128 bits (16 bytes) by definition. So there’s no need to convert it to binary. It already is. Unless you’re working with a stringified version of the uuid7.

[yepyoukno]

Oh yes, I meant don’t store as an ID in its string format!

[dexterdog]

It's just s dumb as storing dates as strings, but people still do it.

[littlecranky67]

But SQLite does not have a native datetime type so you have to use strings

[voakbasda]

You can use an integer

[Volundr]

How do I know the time zone of an integer? Sure there are plenty of cases where one doesn't care, but there are also many cases where the original time zone is important.

[littlecranky67]

other comment said it already, timezone information is not saved. Easiest is just to use a string.

[cenamus]

But also one of the recommended ways of doing it, as it has no native Datetime type.

[antihero]

Doesn't Postgres' UUID type just do this for you anyway?

Why would you store it as as str column and not the inbuilt type for this?

https://www.postgresql.org/docs/current/datatype-uuid.html

If you are using SQLite well I guess that doesn't work.