Devart Forums

Hi there!

DB: MariaDB 10.0.17
dbForge: 6.3.341

With the following schema reverse engineered from a running database:
CREATE TABLE IF NOT EXISTS `daily.event.summary` (
day CHAR(16) DEFAULT NULL,
patientId VARCHAR(128) DEFAULT NULL,
providerId VARCHAR(128) DEFAULT NULL,
patientName VARCHAR(128) DEFAULT NULL,
providerName VARCHAR(128) DEFAULT NULL,
id BIGINT(20) NOT NULL AUTO_INCREMENT,
riskCount BIGINT(20) DEFAULT 0,
eventCount BIGINT(20) DEFAULT 0,
PRIMARY KEY USING BTREE (id),
INDEX daily_summary_patient_idx USING BTREE (patientId),
INDEX daily_summary_provider_idx USING BTREE (providerId),
INDEX des_ckey_idx USING BTREE (day, providerId, patientId, riskCount),
UNIQUE INDEX des_ckey_uidx USING BTREE (day, providerId, patientId),
INDEX des_day_risks_idx USING BTREE (day, riskCount),
INDEX des_names_idx USING BTREE (day, providerName, patientName)
)
ENGINE = TOKUDB
AUTO_INCREMENT = 741693
AVG_ROW_LENGTH = 126
CHARACTER SET utf8
COLLATE utf8_general_ci;

The project build fails with:

daily_event_summary.Table.sql (22, 11): error: Unexpected symbol 'TOKUDB'
daily_event_summary.Table.sql (26, 2): error: Unexpected symbol 'COLLATE'

Am I doing something wrong?

Terry

This happens due to being TOKUDB not supported in dbForge.

You can vote for the following suggestion on our UserVoice forum http://devart.uservoice.com/forums/7729 ... age-engine

We collect and analyze the information from this forum in order to make a proper roadmap for future product releases.

Thanks for getting back to me.

OK, that makes sense, but why is COLLATE being marked as an error?

Perhaps the feature that is needed isn't adding TOKUDB support, but to allow us to declare certain engines as safe without validation, as in the statement I posted, there is nothing syntactically wrong.

t.

If you replace TOKUDB with, for example, INNODB:

CREATE TABLE IF NOT EXISTS `daily.event.summary` (
day CHAR(16) DEFAULT NULL,
patientId VARCHAR(128) DEFAULT NULL,
providerId VARCHAR(128) DEFAULT NULL,
patientName VARCHAR(128) DEFAULT NULL,
providerName VARCHAR(128) DEFAULT NULL,
id BIGINT(20) NOT NULL AUTO_INCREMENT,
riskCount BIGINT(20) DEFAULT 0,
eventCount BIGINT(20) DEFAULT 0,
PRIMARY KEY USING BTREE (id),
INDEX daily_summary_patient_idx USING BTREE (patientId),
INDEX daily_summary_provider_idx USING BTREE (providerId),
INDEX des_ckey_idx USING BTREE (day, providerId, patientId, riskCount),
UNIQUE INDEX des_ckey_uidx USING BTREE (day, providerId, patientId),
INDEX des_day_risks_idx USING BTREE (day, riskCount),
INDEX des_names_idx USING BTREE (day, providerName, patientName)
)
ENGINE = INNODB
AUTO_INCREMENT = 741693
AVG_ROW_LENGTH = 126
CHARACTER SET utf8
COLLATE utf8_general_ci;

COLLATE will not be marked as an error, because when the parser first meets TOKUDB, it starts working not correctly due to being TOKUDB unrecognized.