jmiller
8a85370e32
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 34s
02.56.01.sql used PREPARE/EXECUTE/DEALLOCATE to conditionally drop the 26 legacy remote_storage/ftp_*/sftp_*/gdrive_*/s3_* columns portably. Joomla's installer rejects those statements on MySQL 8 (error 1295: "This command is not supported in the prepared statement protocol yet"), aborting the whole component install when updating from an old schema. Neutralize 02.56.01.sql (now a no-op comment) and move the purge into Pkg_MokoSuiteBackupInstallerScript::dropLegacyRemoteColumns(): gate on INFORMATION_SCHEMA, then issue one plain ALTER dropping only the columns that still exist — portable on MariaDB and MySQL 8, idempotent, non-fatal. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i
14 lines
886 B
SQL
14 lines
886 B
SQL
-- Legacy single-remote storage columns are now purged by the package installer
|
|
-- script (Pkg_MokoSuiteBackupInstallerScript::dropLegacyRemoteColumns()), NOT here.
|
|
--
|
|
-- The 26 legacy remote_storage/ftp_*/sftp_*/gdrive_*/s3_* columns must be removed
|
|
-- portably across MariaDB and MySQL 8. `DROP COLUMN IF EXISTS` is MariaDB-only
|
|
-- (errors on MySQL 8); plain `DROP COLUMN` errors when a column is absent. The
|
|
-- previous version gated the ALTER on INFORMATION_SCHEMA and ran it via
|
|
-- PREPARE/EXECUTE/DEALLOCATE — but those statements are rejected by Joomla's
|
|
-- installer SQL path (MySQL error 1295: "This command is not supported in the
|
|
-- prepared statement protocol yet"), which ABORTED the whole component install.
|
|
--
|
|
-- The drop is now done in PHP (INFORMATION_SCHEMA gate + a plain ALTER for only the
|
|
-- columns that still exist), so this migration is intentionally a no-op.
|