v.25.11Improvement

Versions, the setting create_table_empty_primary_key_by_default was ineffective

In previous versions, the setting create_table_empty_primary_key_by_default was ineffective when you didn't specify the table engine in the CREATE TABLE query. #89342 (Alexey Milovidov).
The setting create_table_empty_primary_key_by_default now works correctly even when the table engine is not specified in the CREATE TABLE query.

Why it matters

Previously, the create_table_empty_primary_key_by_default setting was ineffective if the user did not specify the table engine during table creation. This fix ensures that the setting is respected regardless of whether the engine is specified, improving consistency and user control over primary key creation behavior.

How to use it

To enable this feature, set the create_table_empty_primary_key_by_default setting as desired in your server or user configuration. Then create tables without specifying the table engine; the setting will now be applied properly to generate an empty primary key by default.