Skip to content
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.

Sign up for GitHub

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

Jump to bottom

big_increments not treated as primary key #371

Closed
jpmateo022 opened this issue Feb 4, 2021 · 0 comments · Fixed by #374
Closed

big_increments not treated as primary key #371

jpmateo022 opened this issue Feb 4, 2021 · 0 comments · Fixed by #374
Labels
bug An existing feature is not working as intended enhancement A feature that exists, works as intended but needs to be improved

Comments

@jpmateo022
Copy link

In migration, big_increments()is not treated as the primary key, it will require a .primary() to mark it as primary white the increment() is treated as the primary key.
@jpmateo022 jpmateo022 added the bug An existing feature is not working as intended label Feb 4, 2021
@josephmancuso josephmancuso added the enhancement A feature that exists, works as intended but needs to be improved label Feb 4, 2021
@josephmancuso josephmancuso mentioned this issue Feb 5, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug An existing feature is not working as intended enhancement A feature that exists, works as intended but needs to be improved
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature/371 MasoniteFramework/orm
2 participants
@josephmancuso @jpmateo022