[Bug]: Allow to configure intial page number

[hantsy]

Specification Version

1.0.1

Bug report

I have used Quarkus, Spring Data, and Micronaut Data, all of which provide pagination features. However, by default, the initial page number is 0.

It is a start number convention in Java language(except for reading JDBC field positions).

But in Jakarta Data spec, it seems the pagination starts at 1, which confused me, and I had to adjust my usage in the previous experience.

I hope there is a config to setup the initial page number is 0 or 1.

Let's developers decide.

Additional information

No response

[gavinking]

I noticed this when we were working on 1.0, and thought it was a little bit strange (the equivalent Page object in Hibernate has 0-based indexing) but I didn't think it was worth arguing about. Sorry about that.

But 1.0 is already final, so we should not be messing about and changing this now.

It is a start number convention in Java language(except for reading JDBC field positions).

It's certainly more common in Java, but IIRC there's also places in JPA and in JPQL where indexing is 1-based so people just need to be on the lookout for that. 0-based indexing is not a universal convention.

[gavinking]

Note that Limit.startAt is also 1-based, so Jakarta Data is self-consistent here (though it does disagree with JPA's setFirstResult()).