It could be long in application layer (C#, Java), but then would be converted by algorithm to {TableName + int RowId} when it is a time to retrieve that data.
Or even keep in application layer {TableId, RowId} like you suggested.
I mean the key idea is to use int in database indexes instead of long.
I know that RDBMS starts to have serious issues at scale. That's why I prefer to use int.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2015-10-02 08:33 pm (UTC)It could be long in application layer (C#, Java), but then would be converted by algorithm to {TableName + int RowId} when it is a time to retrieve that data.
Or even keep in application layer {TableId, RowId} like you suggested.
I mean the key idea is to use int in database indexes instead of long.
I know that RDBMS starts to have serious issues at scale.
That's why I prefer to use int.