-
Notifications
You must be signed in to change notification settings - Fork 898
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
Explicitly specify the primary key for the metrics tables #18384
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we have a good chance of merging the schema changes, then maybe we can merge this PR sooner rather than later?
It doesn't really have bad downside. because lets face it, the primary key will always be id
or this table
Required for ManageIQ/manageiq-schema#327 |
Can we also verify that there are specs on creation and querying? My main concern is that triggers/views are finicky on ActiveRecord insert as that AR insert requires that the id comes back from a create. |
a7b736a
to
7ea5163
Compare
This is required as a view doesn't have a primary key, so active record can't fetch the value by default.
7ea5163
to
68f3082
Compare
Checked commit carbonin@68f3082 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
This is required as a view doesn't have a primary key, so
active record can't fetch the value by default.