Given the following structure of the sample table, is there a way to add to the unique constraint to ensure that the combination is unique (GUID, 'Y')?
Application logic - updating guid creates a new version with the same guid but new luid ; and the previous one is inactive ('Y' β 'N')
GUID - external identifier
LUID - internal identifier
create table id_active( "GUID" RAW(16) NOT NULL, "LUID" RAW(16) NOT NULL, "IS_ACTIVE" char(1) NOT NULL CHECK ( "IS_ACTIVE" IN ('Y', 'N')), PRIMARY KEY ("GUID", "LUID"),
source share