covert the sql from mysql to postgres format, error

[hpujsj]

mysql:

CREATE TABLE fa_admin (
id int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'ID',
username varchar(20) COLLATE utf8mb4_unicode_ci DEFAULT '' COMMENT '用户名',
nickname varchar(51) COLLATE utf8mb4_unicode_ci DEFAULT NULL COMMENT '昵称',
password varchar(32) COLLATE utf8mb4_unicode_ci DEFAULT '' COMMENT '密码',
salt varchar(30) COLLATE utf8mb4_unicode_ci DEFAULT '' COMMENT '密码盐',
avatar varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT '' COMMENT '头像',
email varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT '' COMMENT '电子邮箱',
mobile varchar(11) COLLATE utf8mb4_unicode_ci DEFAULT '' COMMENT '手机号码',
loginfailure tinyint(1) unsigned NOT NULL DEFAULT '0' COMMENT '失败次数',
logintime bigint(16) DEFAULT NULL COMMENT '登录时间',
loginip varchar(50) COLLATE utf8mb4_unicode_ci DEFAULT NULL COMMENT '登录IP',
createtime bigint(16) DEFAULT NULL COMMENT '创建时间',
token varchar(59) COLLATE utf8mb4_unicode_ci DEFAULT '' COMMENT 'Session标识',
status varchar(30) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'normal' COMMENT '状态',
PRIMARY KEY (id),
UNIQUE KEY username (username) USING BTREE
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='管理员表';

postgress:
CREATE TABLE "fa_admin" (
  "id" INTEGER NOT NULL  COMMENT 'ID',
  "username" varchar(20) DEFAULT '' COMMENT '用户名',
  "nickname" varchar(51) DEFAULT NULL COMMENT '昵称',
  "password" varchar(32) DEFAULT '' COMMENT '密码',
  "salt" varchar(30) DEFAULT '' COMMENT '密码盐',
  "avatar" varchar(255) DEFAULT '' COMMENT '头像',
  "email" varchar(100) DEFAULT '' COMMENT '电子邮箱',
  "mobile" varchar(11) DEFAULT '' COMMENT '手机号码',
  "loginfailure" BOOLEAN NOT NULL DEFAULT '0' COMMENT '失败次数',
  "logintime" BIGINT DEFAULT NULL COMMENT '登录时间',
  "loginip" varchar(50) DEFAULT NULL COMMENT '登录IP',
  "createtime" BIGINT DEFAULT NULL COMMENT '创建时间',
  "token" varchar(59) DEFAULT '' COMMENT 'Session标识',
  "status" varchar(30) NOT NULL DEFAULT 'normal' COMMENT '状态',
  PRIMARY KEY ("id"),
  UNIQUE KEY "username" ("username") USING BTREE
) =2 COMMENT='管理员表';

[HelgeSverre]

Fixed in v1.13.7 (published to crates.io and GitHub Releases).

Root cause: converting the table-level ENGINE=... AUTO_INCREMENT=2 ... COMMENT='...' options left a dangling ) =2 COMMENT='...';, and MySQL-only syntax (inline column COMMENT 'text', UNIQUE KEY \name` (`col`) USING BTREE`) was passed through unchanged instead of being converted/stripped for PostgreSQL.

Converting your exact SQL now produces valid PostgreSQL:

CREATE TABLE "fa_admin" (
  "id" INTEGER NOT NULL,
  "username" varchar(20) DEFAULT '',
  "nickname" varchar(51) DEFAULT NULL,
  "password" varchar(32) DEFAULT '',
  "salt" varchar(30) DEFAULT '',
  "avatar" varchar(255) DEFAULT '',
  "email" varchar(100) DEFAULT '',
  "mobile" varchar(11) DEFAULT '',
  "loginfailure" BOOLEAN NOT NULL DEFAULT false,
  "logintime" BIGINT DEFAULT NULL,
  "loginip" varchar(50) DEFAULT NULL,
  "createtime" BIGINT DEFAULT NULL,
  "token" varchar(59) DEFAULT '',
  "status" varchar(30) NOT NULL DEFAULT 'normal',
  PRIMARY KEY ("id"),
  UNIQUE ("username")
);

Verified against a real PostgreSQL 16 instance. Also covered MySQL prefix-length unique indexes (e.g. UNIQUE KEY `email` (`email`(191))) and made the stripping string-literal-aware so it doesn't touch DEFAULT/CHECK values that happen to contain the words "comment" or "AUTO_INCREMENT".

Fix: 876c7c1

Upgrade with cargo install sql-splitter / brew upgrade sql-splitter / re-pull the Docker image, and this should be resolved. Please reopen if you still see issues.

[HelgeSverre]

@hpujsj