-
Notifications
You must be signed in to change notification settings - Fork 23
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
Keep compatibility with Icinga DB v5 #1114
Conversation
96e85db
to
c57298e
Compare
bad64e8
to
e43e81c
Compare
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.
Works fine.
7d6b136
to
7ca1359
Compare
7ca1359
to
87a203f
Compare
87a203f
to
1ffbe35
Compare
]; | ||
|
||
if (Backend::getDbSchemaVersion() >= 6) { |
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.
Since Icinga DB 1.2.1
was released last year without any changes to dependencies, this should be updated to schema version 7
accordingly.
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.
@sukhwinder33445 Please do so.
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.
Btw. The used schema version isn't the same for both supported DBMs, i.e. current MySQL schema version is 6
, while for PostgreSQL, it is 4
. Is this distinction not relevant in this context?
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.
Ups, yes, it is relevant.
blocked by #1112