As described in EZP-29915, the options defined for ezselection Field Type Definition should be translatable.

In order to do it, database schema upgrade is required.

The Legacy Storage schema requires new table defined as follows:

• For MySQL:

  DROP TABLE IF EXISTS ezcontentclass_attribute_ml;
  CREATE TABLE ezcontentclass_attribute_ml (
      contentclass_attribute_id INT NOT NULL,
      version INT NOT NULL,
      language_id BIGINT NOT NULL,
      name VARCHAR(255) NOT NULL,
      description TEXT,
      data_text TEXT,
      data_json TEXT, -- since MySQL 5.7 it will be JSON,
      PRIMARY KEY (contentclass_attribute_id, version, language_id),
      CONSTRAINT ezcontentclass_attribute_ml_attr_fk FOREIGN KEY (contentclass_attribute_id) REFERENCES ezcontentclass_attribute (id) ON DELETE CASCADE ON UPDATE CASCADE,
      CONSTRAINT ezcontentclass_attribute_ml_lang_fk FOREIGN KEY (language_id) REFERENCES ezcontent_language (id) ON DELETE CASCADE ON UPDATE CASCADE
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
  

• For PostgreSQL:

  CREATE TABLE ezcontentclass_attribute_ml (
      contentclass_attribute_id INT NOT NULL,
      version INT NOT NULL,
      language_id BIGINT NOT NULL,
      name VARCHAR(255) NOT NULL,
      description TEXT,
      data_text TEXT,
      data_json TEXT,
      PRIMARY KEY (contentclass_attribute_id, version, language_id),
      CONSTRAINT ezcontentclass_attribute_ml_lang_fk FOREIGN KEY (language_id) REFERENCES ezcontent_language (id) ON DELETE CASCADE ON UPDATE CASCADE
  );
  

The change requires for MySQL upgrade script also and for PostgreSQL just an upgrade script (unless full PostgreSQL support will be ready before merging).