#Inquiry: id Column in refresh_state_references Table Exceeds Integer Limit

1 messages · Page 1 of 1 (latest)

worthy dune
#

Dear Backstage Team,

I am reaching out to inquire about the id column in the refresh_state_references table used by the Backstage backend. We have encountered an issue where the value of this column has reached the upper limit of the 32-bit integer data type, as entities are deleted and reinserted—even when only updated here in the code. This results in significant gaps in the id values, since they are auto-incremented. Current version of backstage backend we are using is 1.27
To resolve the issue initially, we changed the data type of the id column from int to bigint. Could you please confirm whether there are any plans to migrate this column to a bigint data type in upcoming releases? Additionally, we would appreciate any guidance or best practices you recommend for handling this scenario in the current version.

summer wedge
#

Oh, no - that should absolutely be a bigIncrements

#

If you can make a migration PR for that, we'd be grateful

worthy dune
#

I was trying to create an issue in backstage OSS related to the id column in the refresh_state_references table, but I received an error: 'Unable to create issue.' Could I get some help with this?

image.png image.png
summer wedge
worthy dune
#

Thank you so much for your support.

worthy dune
#

Hi @freben, just wanted to check for future reference—do you know why I wasn't able to create an issue?

shell wagon
#

If you’re using an enterprise GitHub account that could be why. I had the same issue at my previous employer. The Backstage repo has no controls to block people from submitting issues in place. 👍🏻