Store table should use bigint not int

[mekarpeles]

Problem

Our production store table has 338,283,267 (38M) rows, data has 160M and both use int for its id which will max at around 2B ids (which we're far off from but) as we migrate from ol-db1 to ol-db0 we should make sure all our large tables (e.g. data, thing) should use bigint.

Related to #5675 / #9155

Instructions for Contributors

• Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.

[jimchamp]

Related to #5675

[khattabx]

Hey @mekarpeles , @jimchamp after building the project, I took a tour through it to understand the codebase. I also reviewed the documentation and learned how this org uses Git, Docker, and pre-commit.

I would like to take this issue and start working on it.

Note: I am a new one here if this issue not good for starting with if you can please mention another one and until you can replay on this i'll working on it.

[jimchamp]

I'm planning to do this during the DB migration.

@khattabx, I'm not sure if we have any good first issues today, nor do I remember what your specialties are (front-end, back-end, etc.). Maybe you can find something that you'd like to work on here?

The above link lists issues that have the following criteria:

• The issues have no assignee (meaning: nobody is working on them)
• The issues have been triaged by Open Library staff, and have a lead that can provide support to contributors should they need help
• The issues have been created relatively recently (the older the issue, the less likely that it is still relevant and up-to-date)

I suggest asking to be assigned to issues before writing code, and gathering information about anything that may seem confusing or contradictory. Staff is fairly overwhelmed at the moment, so expect responses to be a it slow. I believe that you have access to our Slack -- If we are taking too long to respond, it's totally fine to gently remind the issue's lead that you are awaiting a response on an issue.

[khattabx]

Thanks @jimchamp, yes i have access on the slack, i'll be active more on it. and also thanks for helping and tell me what to do before coding i'll try to choose issue that related to my specialties(Data Engineering) or if you know any one i can solve it assign it to me and i'll doing my best.

Note: any issue that make me knowing more about the DB and DB codebase i'll do my best to solve because this issue will give me more experience.