Rahul Thakur wrote:
'int' ids are now converted to 'long' across the project and to allow really large values. This should cater to scenarios where the id generation could be started from an arbitrary large value.

Won't this break the API?

Yep, it would.


What is the use case where 4 billion IDs isn't sufficient?

2 billion you mean :-). But this also more of something that I have noticed 'traditionally' that ids are specified as long and stored as bigints in database

No, 4 billion. an int is +-2billion. Anyway, just because longs are more traditionally used that is not a good enough reason to switch to longs and break the API to me.

--
Trygve

Reply via email to