Standard way to control initial value of @Version

[quaff]

Test rely on version value assertion is failed when switch from Hibernate to EclipseLink, because Hibernate starts from 0 but EclipseLink starts from 1, It would be nice if the spec enforce it.
I'd like it starts from 1 because it's human readable then can be display in UI directly.

[gavinking]

The most obvious way to do this is to let you write:

@Version
int version = 1;

and I have a feeling Hibernate already lets you do that.

[quaff]

@Version
int version = 1;

Both of Hibernate and EclipseLink works fine, perhaps we should repurpose the issue to make this feature official, any non-negative integer initial value will be the seed of version, negative or null initial value is considered as undefined and vendor is free to handle it.

[gavinking]

Both of Hibernate and EclipseLink works fine, perhaps we should repurpose the issue to make this feature official

That sounds good to me.

any non-negative integer initial value will be the seed of version, negative or null initial value is considered as undefined and vendor is free to handle it.

Yes.

[quaff]

EclipseLink treats int version = 0 and Integer version = 0 as Integer version = null, so the word non-negative should be revised to positive.

[quaff]

Superseded by #649.

[quaff]

@gavinking timestamp version applies here too, think about

@Version
LocalDateTime version = LocalDateTime.of(...);

Which one should be the initial value, LocalDateTime.of(...) or LocalDateTime.now() ? Hibernate use the former, but I think now() is better.

[gavinking]

timestamp version applies here too

Yes, sure, I know.