New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be able to use .primary() as for unique() constraint #207
Comments
@girardinsamuel increments is special. Increments assumes that its the primary key. increments is the same as "auto incrementing primary column" version of the table so its a bit of an all-in-one. What we really need to to be able to specify any one of the other column types as a primary key like: table.unsigned_integer('col').primary() |
@josephmancuso Yes that was a bad example but that's what I had in mind. I will update the PR then |
ok great just making sure :) |
I have updated the test in the PR, when I am using .primary() on a simple integer column |
Be able on a migration to use primary() this way:
The text was updated successfully, but these errors were encountered: