|
@@ -3,7 +3,7 @@
|
3
|
3
|
#
|
4
|
4
|
# PLEASE consider using mysql with innodb tables to avoid locking issues
|
5
|
5
|
#
|
6
|
|
-# In your Quartz properties file, you'll need to set
|
|
6
|
+# In your Quartz properties file, you'll need to set
|
7
|
7
|
# org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.StdJDBCDelegate
|
8
|
8
|
#
|
9
|
9
|
|
|
@@ -84,7 +84,7 @@ CREATE TABLE QRTZ_CRON_TRIGGERS
|
84
|
84
|
);
|
85
|
85
|
|
86
|
86
|
CREATE TABLE QRTZ_SIMPROP_TRIGGERS
|
87
|
|
- (
|
|
87
|
+ (
|
88
|
88
|
SCHED_NAME VARCHAR(120) NOT NULL,
|
89
|
89
|
TRIGGER_NAME VARCHAR(200) NOT NULL,
|
90
|
90
|
TRIGGER_GROUP VARCHAR(200) NOT NULL,
|
|
@@ -100,7 +100,7 @@ CREATE TABLE QRTZ_SIMPROP_TRIGGERS
|
100
|
100
|
BOOL_PROP_1 VARCHAR(1) NULL,
|
101
|
101
|
BOOL_PROP_2 VARCHAR(1) NULL,
|
102
|
102
|
PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
|
103
|
|
- FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
|
|
103
|
+ FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
|
104
|
104
|
REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
|
105
|
105
|
);
|
106
|
106
|
|
|
@@ -126,7 +126,7 @@ CREATE TABLE QRTZ_CALENDARS
|
126
|
126
|
CREATE TABLE QRTZ_PAUSED_TRIGGER_GRPS
|
127
|
127
|
(
|
128
|
128
|
SCHED_NAME VARCHAR(120) NOT NULL,
|
129
|
|
- TRIGGER_GROUP VARCHAR(200) NOT NULL,
|
|
129
|
+ TRIGGER_GROUP VARCHAR(200) NOT NULL,
|
130
|
130
|
PRIMARY KEY (SCHED_NAME,TRIGGER_GROUP)
|
131
|
131
|
);
|
132
|
132
|
|
|
@@ -160,7 +160,7 @@ CREATE TABLE QRTZ_SCHEDULER_STATE
|
160
|
160
|
CREATE TABLE QRTZ_LOCKS
|
161
|
161
|
(
|
162
|
162
|
SCHED_NAME VARCHAR(120) NOT NULL,
|
163
|
|
- LOCK_NAME VARCHAR(40) NOT NULL,
|
|
163
|
+ LOCK_NAME VARCHAR(40) NOT NULL,
|
164
|
164
|
PRIMARY KEY (SCHED_NAME,LOCK_NAME)
|
165
|
165
|
);
|
166
|
166
|
|