Exponential Platform Nexus v1.1.0.13 — the demo installs on MySQL and MariaDB

Fixed

• exponential:install exponential-media works on MySQL and MariaDB. Up to v1.1.0.12 it stopped at once with DBMS-specific file for mysql database platform does not exist or is not readable: the line shipped the extra schema of the demo (Netgen Layouts, Netgen Tags, SEO metas, enhanced selection) for SQLite only.
• New data/mysql/media_schema.sql: the same 28 tables as the SQLite file, columns in the same order (the demo data's INSERT statements carry no column lists), ids AUTO_INCREMENT as Netgen Layouts and the Tags Bundle expect on MySQL, utf8mb4_unicode_520_ci like the rest of the schema.
• The MySQL demo data fits the Platform 3.3 schema. data/mysql/media_data.sql had been dumped from a database of the next platform generation: every ezcontentclassgroup row had a seventh value (is_system), and it locked 25 tables without rows that this schema does not have (ibexa_setting, ibexa_token, ibexa_user_invitations, ezinfocollection and others). Both are removed; the file now holds the same 61 tables, 11718 rows and values as the SQLite data.
• New objects in the legacy admin on MySQL and MariaDB. When the legacy schema completion gave a table its composite primary key (for example ezcontentobject_attribute (id, version)), it removed AUTOINCREMENT from the serial column on every engine, not only on SQLite, where that is needed. On MySQL and MariaDB the legacy kernel lets the database number new rows, so every new object after the first failed with Duplicate entry '0-1' for key 'PRIMARY' (an image upload in the legacy admin answered 500). Now only SQLite loses it, and on the other engines every serial column of the legacy schema gets AUTO_INCREMENT back where it is missing (11 tables). A database installed before is repaired with bin/console exponential:legacy:complete-schema.

Documentation

• doc/INSTALL.md and chapter 4.5 of the book: the 1.1 demo installs on SQLite, MySQL and MariaDB; with MariaDB give its version in DATABASE_URL (serverVersion=mariadb-10.5.29); why older tags failed on MySQL. PostgreSQL still has no demo schema on this line.

Verified

Fresh installs of this commit, every package as released from Packagist (no path repositories), Composer's security blocking on, the steps of doc/INSTALL.md (.env.local with the MySQL DATABASE_URL, exponential:install exponential-media, yarn, assets, keys, GraphQL schema, cache), each step exiting 0:

• MariaDB 10.5 on PHP 8.5 and on PHP 8.0: the site pages, the admin UI, ngadminui and legacy_admin sign-ins pass; in the legacy admin, three runs of three rounds each (publish rich text with a link, upload an image, bookmarks, bookmark folder, search) pass; every content version keeps all its attribute rows; all 133 legacy tables have the legacy primary key and their serial columns are AUTO_INCREMENT; no legacy error.log lines, no prod.log errors.
• SQLite on PHP 8.5, the same checks: all pass, as on v1.1.0.12 (all 133 legacy tables with the legacy primary key).
• An existing MariaDB database installed with the previous code (11 serial columns without AUTO_INCREMENT) is repaired by exponential:legacy:complete-schema (11 statements, the check then passes).

Not covered: PostgreSQL (no demo schema on this line), MySQL server builds other than MariaDB 10.5 were not run.