Skip to content
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 column external_uuid to contact and contactgroup #192

Open
nilmerg opened this issue May 3, 2024 · 1 comment · May be fixed by #216
Open

Add column external_uuid to contact and contactgroup #192

nilmerg opened this issue May 3, 2024 · 1 comment · May be fixed by #216

Comments

@nilmerg
Copy link
Member

nilmerg commented May 3, 2024

It should be NOT NULL and of type CHAR(36).

Required by Icinga/icinga-notifications-web#176

@julianbrost
Copy link
Collaborator

PostgreSQL provides a dedicated uuid data type where you shouldn't even notice a difference to char(36) if you just store lower-case hexadecimal UUIDs with four dashes in the usual places (it just accepts other UUID representations as well and normalizes them), so uuid for PostgreSQL and char(36) for MySQL/MariaDB could be an option as well. (MariaDB ≥ 10.7 also has a UUID type, but using it would require case distinction within the MySQL/MariaDB schema.)

Another option would be to use bytea (with length 16) in PostgreSQL and binary(16) in MySQL, similar to how we store the object.id already and also how Icinga DB stores IDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants