-
Notifications
You must be signed in to change notification settings - Fork 9
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
Feature Request: Add support for BIGINT Identity Columns #10
Comments
Thanks, this is a good idea for feature enhancement. SQL Server does support various integer based numeric data types as But GUID is not supported as an |
Sorry I should have described the GUID use case better as a primary key. I was thinking the library could generate relations based on a GUID rather than the identity column. I am seeing this design more frequently as of late in lieu of the identity column. I am guessing that is a can of worms though ;-) This framework here uses GUIDS by default instead of identity columns. You can however use int and bigint. Thanks again for this library. I look forward to future releases. |
This is now implemented ✅ and merged into |
Now released with v2.2 |
Currently the library only supports INT identity columns. Would be nice to support BIGINT for different design scenarios. i.e. multi-tenant SAAS applications. GUIDS are another use case, but probably not easy to implement.
Thanks!
The text was updated successfully, but these errors were encountered: