use "ENGINE=InnoDB" rather than deprecated "TYPE=InnoDB"

00raq00 · Sep 8, 2013 · e5c8829 · e5c8829
1 parent f88015c
commit e5c8829
Showing 1 changed file with 11 additions and 11 deletions.
diff --git a/database/tables/tables_mysql_innodb.sql b/database/tables/tables_mysql_innodb.sql
@@ -25,7 +25,7 @@ IS_UPDATE_DATA BOOLEAN NOT NULL,
 REQUESTS_RECOVERY BOOLEAN NOT NULL,
 JOB_DATA BLOB NULL,
 PRIMARY KEY (SCHED_NAME,JOB_NAME,JOB_GROUP))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_TRIGGERS (
 SCHED_NAME VARCHAR(120) NOT NULL,
@@ -47,7 +47,7 @@ JOB_DATA BLOB NULL,
 PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
 FOREIGN KEY (SCHED_NAME,JOB_NAME,JOB_GROUP)
 REFERENCES QRTZ_JOB_DETAILS(SCHED_NAME,JOB_NAME,JOB_GROUP))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_SIMPLE_TRIGGERS (
 SCHED_NAME VARCHAR(120) NOT NULL,
@@ -59,7 +59,7 @@ TIMES_TRIGGERED BIGINT(10) NOT NULL,
 PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
 FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
 REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_CRON_TRIGGERS (
 SCHED_NAME VARCHAR(120) NOT NULL,
@@ -70,7 +70,7 @@ TIME_ZONE_ID VARCHAR(80),
 PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
 FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
 REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_SIMPROP_TRIGGERS
   (          
@@ -91,7 +91,7 @@ CREATE TABLE QRTZ_SIMPROP_TRIGGERS
     PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
     FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) 
     REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_BLOB_TRIGGERS (
 SCHED_NAME VARCHAR(120) NOT NULL,
@@ -102,20 +102,20 @@ PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),
 INDEX (SCHED_NAME,TRIGGER_NAME, TRIGGER_GROUP),
 FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)
 REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_CALENDARS (
 SCHED_NAME VARCHAR(120) NOT NULL,
 CALENDAR_NAME VARCHAR(200) NOT NULL,
 CALENDAR BLOB NOT NULL,
 PRIMARY KEY (SCHED_NAME,CALENDAR_NAME))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_PAUSED_TRIGGER_GRPS (
 SCHED_NAME VARCHAR(120) NOT NULL,
 TRIGGER_GROUP VARCHAR(200) NOT NULL,
 PRIMARY KEY (SCHED_NAME,TRIGGER_GROUP))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_FIRED_TRIGGERS (
 SCHED_NAME VARCHAR(120) NOT NULL,
@@ -132,21 +132,21 @@ JOB_GROUP VARCHAR(200) NULL,
 IS_NONCONCURRENT BOOLEAN NULL,
 REQUESTS_RECOVERY BOOLEAN NULL,
 PRIMARY KEY (SCHED_NAME,ENTRY_ID))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_SCHEDULER_STATE (
 SCHED_NAME VARCHAR(120) NOT NULL,
 INSTANCE_NAME VARCHAR(200) NOT NULL,
 LAST_CHECKIN_TIME BIGINT(19) NOT NULL,
 CHECKIN_INTERVAL BIGINT(19) NOT NULL,
 PRIMARY KEY (SCHED_NAME,INSTANCE_NAME))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE TABLE QRTZ_LOCKS (
 SCHED_NAME VARCHAR(120) NOT NULL,
 LOCK_NAME VARCHAR(40) NOT NULL,
 PRIMARY KEY (SCHED_NAME,LOCK_NAME))
-TYPE=InnoDB;
+ENGINE=InnoDB;
 
 CREATE INDEX IDX_QRTZ_J_REQ_RECOVERY ON QRTZ_JOB_DETAILS(SCHED_NAME,REQUESTS_RECOVERY);
 CREATE INDEX IDX_QRTZ_J_GRP ON QRTZ_JOB_DETAILS(SCHED_NAME,JOB_GROUP);