GUACAMOLE-220: Correct documentation of update script.

The UNIQUE constraint is being added once the column is expected to be
unique, not necessarily because it should safely point to entries of a
particular table.
This commit is contained in:
Michael Jumper
2018-09-27 20:15:23 -07:00
parent 7521cdc0ae
commit bb6e8bc1c7
3 changed files with 3 additions and 3 deletions

View File

@@ -145,7 +145,7 @@ UPDATE guacamole_user SET entity_id = (
-- The entity_id column should now be safely non-NULL
ALTER TABLE guacamole_user MODIFY entity_id int(11) NOT NULL;
-- The entity_id column should now safely point to guacamole_entity entries
-- The entity_id column should now be unique for each user
ALTER TABLE guacamole_user
ADD CONSTRAINT guacamole_user_single_entity
UNIQUE (entity_id);

View File

@@ -155,7 +155,7 @@ UPDATE guacamole_user SET entity_id = (
ALTER TABLE guacamole_user
ALTER COLUMN entity_id SET NOT NULL;
-- The entity_id column should now safely point to guacamole_entity entries
-- The entity_id column should now be unique for each user
ALTER TABLE guacamole_user
ADD CONSTRAINT guacamole_user_single_entity
UNIQUE (entity_id);

View File

@@ -202,7 +202,7 @@ GO
ALTER TABLE [guacamole_user]
ALTER COLUMN [entity_id] [int] NOT NULL;
-- The entity_id column should now safely point to guacamole_entity entries
-- The entity_id column should now be unique for each user
ALTER TABLE [guacamole_user]
ADD CONSTRAINT [AK_guacamole_user_single_entity]
UNIQUE ([entity_id]);