We will be pushing a lot of data into strapi, and it is a concern that we will exceed the max integer range of an autoincrementing ID in Postgres.
Behind the scenes we have modified the tables directly (both the schema tables and relation lookup tables) to be a bigint instead of an integer. This seems to work fine even after reboot/redeployment and records/relations can be created just fine. The only thing I’ve noticed as a side effect is the ID no longer appears in the admin panel as the ID is now a string in the API response (see attached, not a big deal as we expected this).
Are there any concerns with this approach? Is there a recommended way of handling this case?
This topic has been created from a Discord post (1243584183163420753) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord