Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
[Proposal] Switch the default increments() to a bigint #1384
Yes, this will break previous migrations. However we can tackle this in two different ways:
I'd be for this, but the question is whether or not the breaking change goes into 5.8 in Feb, or if we wait for 6.0 (whenever that happens to be).
Do we know of any projects that are using Laravel at scale large enough that this will impact them?
@victorlap's suggestions on moving forward are good, though, and as long as they're covered in the upgrade guide, should be sufficient.
We've done similar before i.e. with the
In the company I work for, we make sure that all ids are bigints, to reduce the likelyhood of running into problems. We do have some projects where this could have gone wrong.