-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add extension required by Icinga Notifications #578
Conversation
As I just needed this today: Happy Birthday little #578 🍰 |
This allows the user to provide the constraint name dynamically, e.g for tables that doesn't have a PK but a `UNIQUE KEY` constraint.
I just took over this PR as I needed a change in Icinga DB (or the future Go library) for Icinga/icinga-notifications#61. Next to rebasing this branch, I added one commit introducing a more precise time type, representing nanoseconds. |
But |
|
After talking with @julianbrost about Icinga/icinga-notifications#61, it turns out that I haven't needed a nanoseconds type. Hooray! This PR and its branch now contains @yhabteab's change, just rebased against the current main branch. |
The changed icingadb dependencies contains the latest state of the noma branch[0] with an additional fix for utils.FromUnixMilli[1,2]. [0]: Icinga/icingadb#578 [1]: Icinga/icingadb#753 [2]: Icinga/icingadb@066abea
The changed icingadb dependencies contains the latest state of the noma branch[0] with an additional fix for utils.FromUnixMilli[1,2]. [0]: Icinga/icingadb#578 [1]: Icinga/icingadb#753 [2]: Icinga/icingadb@066abea
No longer required, since https://github.com/Icinga/icinga-go-library. |
This allows the user to provide the constraint name dynamically, e.g for tables that doesn't have a PK but a
UNIQUE KEY
constraint.