replaced usize with u64 in PaginatorTrait

[liberwang1013]

PR Info

this pr replaced usize with u64 in paginated query.

Changes

• relaced usize with u64 in trait PaginatorTrait
• relaced usize with u64 in struct Paginator

[ikrivosheev]

@liberwang1013 thank you! LGTM!

[tyt2y3]

Thank you for the contribution. Was there an issue/ context that why you think u64 is a better choice than usize?

[liberwang1013]

Thank you for the contribution. Was there an issue/ context that why you think u64 is a better choice than usize?

@tyt2y3
actually the Paginator Wrapped https://docs.rs/sea-orm/0.8.0/sea_orm/entity/prelude/struct.Select.html, they have different input variable types. I hope this can be kept consistent with.

[billy1624]

Thanks for the contributions! @liberwang1013

[billy1624]

Thank you for the contribution. Was there an issue/ context that why you think u64 is a better choice than usize?

Hey @tyt2y3, the context: https://discord.com/channels/873880840487206962/900758376164757555/983627886756003891

[tyt2y3]

Let me think twice 🤔

[ikrivosheev]

@tyt2y3, I review PR: #768 (comment) and here we use: usize. My point is: in pub struct ItemsAndPagesNumber we use usize and here it makes more sense to use usize

[ikrivosheev]

But on the other hand, usize is depends on platform...

[tyt2y3]

Ah. Actually if we decided on that we can change all usize to u64, or the other way around.
Either way it will create a pile of compilation errors.
So I am quite hesitant.

[ikrivosheev]

@tyt2y3, @billy1624 prepared PR for the update sqlx, I think that changing the type is not such a terrible change.

[billy1624]

I think the changes align SeaORM's pagination utility with SeaQuery statement. Because SeaQuery's limit & offset methods both take an u64.

Although it's a breaking change to SeaORM API - changing usize to u64 - but it should be alright since it's a expansion in value range.

[tyt2y3]

Thank you all for your input