DBEAVER 未在 DDSL 中显示 SQL 服务器聚集索引
DBEAVER not showing SQL Server clustered index in DDSL
我在 DBEAVER 21.2.4 和 SQL Server 2019 (v15.0.4178.1) 中遇到以下问题。
每当我看到来自 SQL 服务器 (Script Table > Create as
) 的 DDL 时,它会显示整个约束:
...
CONSTRAINT [PK_Emp] PRIMARY KEY CLUSTERED
(
[EmpID] ASC
)
WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 100,
OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
而只显示 DBEAVER
...
CONSTRAINT PK_Emp PRIMARY KEY (EmpID)
约束中没有数据。
未聚类。不是 Pad_index,没有。
这是 Dbeaver 中的错误,还是我遗漏了什么?
这个
CONSTRAINT [PK_Emp] PRIMARY KEY CLUSTERED
(
[EmpID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 100, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
和
CONSTRAINT PK_Emp PRIMARY KEY (EmpID)
相同,因为 CLUSTERED 是 PRIMARY KEY 约束的默认值,[PRIMARY] 是默认文件组,ALLOW_PAGE_LOCKS 默认为 ON,等等
SSMS 总是明确地编写每个选项的脚本,并且 dbbeaver 显然会忽略它认为使用默认值的选项。
我在 DBEAVER 21.2.4 和 SQL Server 2019 (v15.0.4178.1) 中遇到以下问题。
每当我看到来自 SQL 服务器 (Script Table > Create as
) 的 DDL 时,它会显示整个约束:
...
CONSTRAINT [PK_Emp] PRIMARY KEY CLUSTERED
(
[EmpID] ASC
)
WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 100,
OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
而只显示 DBEAVER
...
CONSTRAINT PK_Emp PRIMARY KEY (EmpID)
约束中没有数据。
未聚类。不是 Pad_index,没有。
这是 Dbeaver 中的错误,还是我遗漏了什么?
这个
CONSTRAINT [PK_Emp] PRIMARY KEY CLUSTERED
(
[EmpID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 100, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
和
CONSTRAINT PK_Emp PRIMARY KEY (EmpID)
相同,因为 CLUSTERED 是 PRIMARY KEY 约束的默认值,[PRIMARY] 是默认文件组,ALLOW_PAGE_LOCKS 默认为 ON,等等
SSMS 总是明确地编写每个选项的脚本,并且 dbbeaver 显然会忽略它认为使用默认值的选项。