Allow customization of foreign key type #23
Replies: 2 comments 2 replies
-
|
Hi, I'm open to the idea. Is it something you could PR? Not sure when I'd be able to look into it myself. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Sure. I think I'll have time next week. |
Beta Was this translation helpful? Give feedback.
-
|
One thing I forgot to mention was; if you publish the migrations you can just make these changes yourself to suit your needs -- if that's easier. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I know. It's easy enough if you understand what the problem is and how to solve it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've tried the package in two different projects, and the migrations failed for different reasons.
In version 5.8, Laravel changed the default primary keys from
INT USIGNEDtoBIGINT UNSIGNEDSo in projects that started before 5.8,users.idis most likely not a bigint.And in a newer project I'm using UUID as primary key on users, in which case you'd have to use this in the migrations:
It's not a huge hassle to edit the migrations manually, but since you already allow some degree of customization of the foreign key, it would be cool if the data type could be customized in config as well.
Beta Was this translation helpful? Give feedback.
All reactions