Add MIN/MAX Ulid constants about ulid-rs HOT 5 CLOSED

ulids are 128-bit identifiers, so the maximum value of u128 is the same as the maximum value of a Ulid. This library implements the From conversion trait to and from u128.

from ulid-rs.

Those constants don't really look like they would be that helpful since they are just 0 or (1 << N) - 1 where N is the bit-width of the field in question. This library does have those N values but they are not currently public. That being said, the python constants don't really solve much of the problem since you would still need to do your own bit-math for range queries.

I think that we should instead design an API that returns std::ops::Range or something similar. Can you explain your use-case some more so that we can come up with an interface that works well?

from ulid-rs.

Hi @dylanhart,

Sure... basically i am storing records in sqlite where the identifiers are ULIDs. By range queries, i meant that i would like to query a certain table whose identifier is a ULID with identifier BETWEEN X and Y or identifier <= {max_ulid_identifier}.

This is why i think the constants might be useful if you want to get records with identifiers greater or smaller than min/max ULIDs respectively.

Would you say that:

use chrono::{MAX_DATETIME, MIN_DATETIME};
use ulid:: Generator;

let mut generator = Generator::new();
let max_ulid = generator.generate_from_datetime(MAX_DATETIME).unwrap();
let min_ulid = generator.generate_from_datetime(MIN_DATETIME).unwrap();

would properly calculate the min and max values?

from ulid-rs.

In that case you can use u128::MAX for now. The min/max datetime would not work at all, so a new API could be added to get ulid value sub-ranges for date ranges along with ulid-specific min/max datetime.

from ulid-rs.

I see... could you elaborate on using u128::MAX please? Do you mean that i could use u128::MAX to generate a ULID?

from ulid-rs.