-
Notifications
You must be signed in to change notification settings - Fork 311
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
Optional identity columns #2201
base: master
Are you sure you want to change the base?
Conversation
… optional_identity_columns
We would love this change. It also would solve #2049. |
… optional_identity_columns
… optional_identity_columns
…e compatible with Ruby 3
If Rails can create proper relationships with the new column type, then I would say, use it by default unless user requested older style primary key. Or course some test cases to show that would be needed. Another thing to consider is migrations and schema dumps with In either case, thorough upgrade docs would be needed. |
@yahonda Sorry to ping directly, but I wonder if you have any reservations about this PR or any guidance on things to improve so it can be accepted. I would love to see this support make it into the gem. |
Let me have some review. |
The goal here is to add optional support for Oracle 12's IDENTITY columns.
This code is probably still in need of some cleanup/adjustments, but I wanted to submit it as a sort of proof-of-concept and get some feedback before I continue working on it.
By default, IDENTITY columns are disabled. They can be enabled in the following ways:
For the whole app via initializer/config:
In migrations:
Please let me know what you think. Thank you!