Resolves Task Lock issue with Oracle DB

In short the Oracle CHAR type is blank padded to the end of the field.  So we were not getting an exact match on queries when looking for the LOCK_KEY or CLIENT_ID
This commit is contained in:
Glenn Renfro
2019-12-20 09:18:59 -05:00
committed by Michael Minella
parent 9faa7fa60e
commit 6b336a983c
2 changed files with 4 additions and 2 deletions

View File

@@ -0,0 +1,2 @@
alter table TASK_LOCK MODIFY LOCK_KEY VARCHAR2(36);
alter table TASK_LOCK MODIFY CLIENT_ID VARCHAR2(36);

View File

@@ -29,9 +29,9 @@ CREATE TABLE TASK_TASK_BATCH (
CREATE SEQUENCE TASK_SEQ START WITH 0 MINVALUE 0 MAXVALUE 9223372036854775807 NOCACHE NOCYCLE;
CREATE TABLE TASK_LOCK (
LOCK_KEY CHAR(36) NOT NULL,
LOCK_KEY VARCHAR2(36) NOT NULL,
REGION VARCHAR2(100) NOT NULL,
CLIENT_ID CHAR(36),
CLIENT_ID VARCHAR2(36),
CREATED_DATE TIMESTAMP NOT NULL,
constraint LOCK_PK primary key (LOCK_KEY, REGION)
);