[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)
commitb45acf94b28a46d6dd9641df928cbc0912831bd1
tree96e9bcf6c91de0edf28a6c7a05379780019970d5
parente008261b4f054e9043ac531289d0a5c4ea000de1
[BUGFIX] Avoid database upgrade failures when adding slug field

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