[BUGFIX] Avoid database upgrade failures when adding slug field 46/58146/5
authorOliver Hader <oliver@typo3.org>
Mon, 3 Sep 2018 17:19:04 +0000 (19:19 +0200)
committerSusanne Moog <susanne.moog@typo3.org>
Mon, 3 Sep 2018 19:29:46 +0000 (21:29 +0200)
When upgrading with e.g. MSSQL it should be noted, that the
pages.slug DB field should be a varchar database field (instead of
"text"), which can be null, allowing the field to be created when
upgrading an instance, without having the upgrade wizard run yet.

So all slug fields are set to null, and can be ommitted correctly.

Resolves: #86116
Releases: master
Change-Id: Iedf62d1a145c25d0ecbc9e25c163255173cdb2d7
Reviewed-on: https://review.typo3.org/58146
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Susanne Moog <susanne.moog@typo3.org>
Tested-by: Susanne Moog <susanne.moog@typo3.org>
typo3/sysext/core/ext_tables.sql

index f430af5..b84d29a 100644 (file)
@@ -76,7 +76,7 @@ CREATE TABLE pages (
        perms_group tinyint(4) unsigned DEFAULT '0' NOT NULL,
        perms_everybody tinyint(4) unsigned DEFAULT '0' NOT NULL,
        title varchar(255) DEFAULT '' NOT NULL,
-       slug text,
+       slug varchar(2048),
        doktype int(11) unsigned DEFAULT '0' NOT NULL,
        TSconfig text,
        is_siteroot tinyint(4) DEFAULT '0' NOT NULL,