int not big enough

[FayeG]

Hi,

We're using the Mysql backend to puppet dashboard.

We recently hit the problem that column "id" in the table resource_statuses was an "int" and not a "bigint" so we ran out of ids to use.

Please could this be fixed. ie. when the table is created in future releases and as a recommendation pre updated. Here's the steps we took to resolve it:

mysql> alter table resource_events drop foreign key fk_resource_events_resource_status_id;
mysql> ALTER TABLE resource_statuses MODIFY COLUMN id BIGINT;
…… long wait ……
mysql> ALTER TABLE resource_events MODIFY COLUMN resource_status_id BIGINT;
mysql> alter table resource_events add CONSTRAINT fk_resource_events_resource_status_id FOREIGN KEY (resource_status_id) REFERENCES resource_statuses (id) ON DELETE CASCADE;
mysql> ALTER TABLE resource_statuses MODIFY COLUMN id BIGINT NOT NULL AUTO_INCREMENT;

[bwitt]

I had to do this for metrics table as well
alter table metrics change id id bigint not null auto_increment;

[bwitt]

let's add a migration to fix this

[unixman99]

yes, I had this happen too, altering the tables didn't seem to fix it for me though, had to db:drop and db:create to get past it.

[crispygoth]

Just came across this myself, although I'm using postgres. Thought I'd add a note to let you know it's not just a MySQL issue.