Feature #17251
closedData type of the id on 'big' tables
Description
Hi,
Could the id columns of tables that are meant to cycle data frequently (like logs, reports and fact_values) have by default a bigger datatype like BIGINT or at least, INT UNSIGNED? For a running service, would it be safe to alter the tables on the go or could that generate conflicts when upgrading Foreman (because of the DB migration scripts)?
In our case they're all of type INT as it was chosen by rails when the initial database was deployed. We have more than 25k nodes running Puppet every hour and we run out of ids way more often than we'd like to.
Maybe there's something that we can do at the time of deploying the application to do this w/o you having to patch anything. Please accept my apologies if that's the case and take this ticket as a question instead of a feature request :)
Thanks.