http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692017-08-17T16:24:53ZTYPO3 ForgeTYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3381902017-08-17T16:24:53ZHans Höchtljhoechtl@gmail.com
<ul></ul><p>Same here, I posted it on Stackoverflow: [[<a class="external" href="https://stackoverflow.com/questions/45737730/typo3-lists-all-tables-in-db-compare-because-of-collate">https://stackoverflow.com/questions/45737730/typo3-lists-all-tables-in-db-compare-because-of-collate</a>]].</p>
<p>I think it could be the collation, not the quotes.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3391462017-09-04T11:35:54ZAleksandar Dimitrov
<ul></ul><p>I was able to reproduce this with 8.7.4 and 8.7.3, and mariadb 10.2.x and 5.x, on clean installs via the Install tool.<br />My guess is that a strict string comparison of <code>''</code> with <code>''''</code> causes the problem.<br />I think the serialisation of the 'original' column definition is buggy. Note the following case:</p>
<pre>
ALTER TABLE `tt_content` CHANGE `table_caption` `table_caption` VARCHAR(255) DEFAULT NULL
Current value: table_caption VARCHAR(255) DEFAULT 'NULL' COLLATE utf8_unicode_ci
</pre>
<p><code>'NULL'</code> is in quotes here, and most definitely should <b>not</b> be, as <code>NULL</code> and <code>'NULL'</code> are very different things for any SQL server. Some aggressive string escaping maybe?</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3411492017-09-25T04:20:18ZMorton Jonuschatm.jonuschat@mojocode.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>On Hold</i></li></ul><p>MariaDB implemented a change to the Information Schema COLUMNS table which changed the output format compared to the original (Oracle) MySQL: <a class="external" href="https://jira.mariadb.org/browse/MDEV-13132">https://jira.mariadb.org/browse/MDEV-13132</a><br />There is ongoing work in the upstream Doctrine DBAL repository on how to fix this: <a class="external" href="https://github.com/doctrine/dbal/pull/2825">https://github.com/doctrine/dbal/pull/2825</a></p>
<p>At this time TYPO3 is not compatible with MariaDB >= 10.2.7 and given that the fix is happening deeply in the upstream Doctrine DBAL stack there is little we can do to work around it at this point in time.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3492752017-10-26T10:22:36ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>On Hold</i> to <i>Rejected</i></li></ul><p>So, the only thing TYPO3 can do, is wait for the Doctrine DBAL fix, and once this is done we can upgrade our dependency.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3511822017-11-20T14:13:55ZGeorg Ringer
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/83046">Bug #83046</a>: sys_file_collection and tt_content could not be created</i> added</li></ul> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3511832017-11-20T14:17:37ZGeorg Ringer
<ul></ul><p>the PR <a class="external" href="https://github.com/doctrine/dbal/pull/2825">https://github.com/doctrine/dbal/pull/2825</a> has been merged yesterday, so lets see when a release is done</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3712212018-08-21T21:34:32ZThomas Böhm
<ul></ul><p>Has this problem been solved? I just installed a fresh typo3 8.7.19 on mariadb 10.2.17 and still have this problem. Or is it solved in mariadb 10.3? Downgrading to 10.1 is not an easy option for me as there are other databases already on that server.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3713842018-08-23T18:57:12ZJan Kiesewetterjan@t3easy.de
<ul></ul><p>TYPO3 8.7 has dbal 2.5.10 locked atm.<br /><a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_8-7/composer.lock#L339-L345">https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_8-7/composer.lock#L339-L345</a><br />and installs maximum v2.5.13.</p>
<p>MariaDB 10.2 support came with doctrine/dbal 2.7.0<br /><a class="external" href="https://github.com/doctrine/dbal/releases/tag/v2.7.0">https://github.com/doctrine/dbal/releases/tag/v2.7.0</a></p>
<p>So this is fixed for master and TYPO3 ^9.3 but not for 8.7.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3889052018-10-17T09:16:17ZGeorg Ringer
<ul></ul><p>Some final words: This won't be solved as doctrine dbal 2.7.0 requires php 7.1 which doesn't fit to the min. requirements of TYPO3 8.7 which got php 7.0.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3889552018-10-18T16:19:52ZJan Kiesewetterjan@t3easy.de
<ul></ul><p>As PHP 7.0 is EOL by 3 Dec 2018 <a class="external" href="http://php.net/supported-versions.php">http://php.net/supported-versions.php</a>, maybe TYPO3 8.7 could raise requirements after that?</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=3930322019-01-03T15:54:19ZThomas Oliver Molltom@fullcircle.de
<ul><li><strong>Priority</strong> changed from <i>Should have</i> to <i>Must have</i></li></ul><p>Jan Kiesewetter wrote:</p>
<blockquote>
<p>As PHP 7.0 is EOL by 3 Dec 2018 <a class="external" href="http://php.net/supported-versions.php">http://php.net/supported-versions.php</a>, maybe TYPO3 8.7 could raise requirements after that?</p>
</blockquote>
<p>This Problem is still present with PHP 7.0 dead for a month now and TYPO3 8.7 still in support for quite some time clinging to the PHP 7.0 requirement doesn't make much sense now.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4048812019-08-20T05:24:19ZArne Bracht
<ul></ul><p>Hello,</p>
<p>I changed /vendor/doctrine/dbal with the dbal 2.7.2 from here: <a class="external" href="https://www.doctrine-project.org/projects/dbal/2.7.html">https://www.doctrine-project.org/projects/dbal/2.7.html</a> within TYPO3 8.7. I think that it worked. Should it be so simple?</p>
<p>I hope it could be integrated in the next TYPO3 8.7.x update. Yes I know it change the PHP requirements from PHP 7.0 to PHP 7.1. But why not? PHP 7.0 is EOL by 3 Dec 2018. And so TYPO3 8.7.27 <= php 7.0 and TYPO3 8.7.28 >= PHP 7.1 should be easily to make a notice in the requirements list and update notice.</p>
<p>Thanks</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4054632019-09-04T09:52:11ZLioh Moeller
<ul></ul><p>Why has this issue been marked as 'rejected'? We still face it with current typo3 version 9.5.9 and still 8.7.x in combination with MariaDB 10.3.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4220412020-04-08T11:33:00ZPascal Naujokspascal.naujoks@pixabit.de
<ul><li><strong>PHP Version</strong> changed from <i>7.1</i> to <i>7.4</i></li></ul><p>Also exists with PHP Version 7.4.4 and 10.4.12-MariaDB-1:10.4.12+maria~stretch on TYPO3 8.7.31</p>
<p>Example of fields that want to be updated but can't:</p>
<pre><code class="text syntaxhl" data-language="text">ALTER TABLE `be_groups` CHANGE `title` `title` VARCHAR(50) DEFAULT '' NOT NULL
Current value: title VARCHAR(50) DEFAULT '''' NOT NULL COLLATE utf8_general_ci
ALTER TABLE `be_groups` CHANGE `allowed_languages` `allowed_languages` VARCHAR(255) DEFAULT '' NOT NULL
Current value: allowed_languages VARCHAR(255) DEFAULT '''' NOT NULL COLLATE utf8_general_ci
ALTER TABLE `be_groups` CHANGE `pagetypes_select` `pagetypes_select` VARCHAR(255) DEFAULT '' NOT NULL
Current value: pagetypes_select VARCHAR(255) DEFAULT '''' NOT NULL COLLATE utf8_general_ci
ALTER TABLE `be_groups` CHANGE `description` `description` VARCHAR(2000) DEFAULT '' NOT NULL
Current value: description VARCHAR(2000) DEFAULT '''' NOT NULL COLLATE utf8_general_ci
...
</code></pre> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4237982020-04-22T15:13:14ZRichard no-lastname-givenrichard.schaufler@gmail.com
<ul><li><strong>PHP Version</strong> changed from <i>7.4</i> to <i>7.2</i></li></ul> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4237992020-04-22T15:13:59ZRichard no-lastname-givenrichard.schaufler@gmail.com
<ul><li><strong>PHP Version</strong> changed from <i>7.2</i> to <i>7.1</i></li></ul> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4238002020-04-22T15:14:10ZRichard no-lastname-givenrichard.schaufler@gmail.com
<ul></ul><p>I can confirm this issue on TYPO3 CMS 8.7.32, PHP 7.2 and MariaDB 10.2.8. My client bought ELTS for security updates. Buying ELTS for security reasons and at the same time not being able to update to MariaDB 10.2 is an issue because support for MariaDB 10.1 will be dropped in October 2020.</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4293062020-08-17T11:44:30ZTim Spiekerkötterdiego@sirdiego.de
<ul></ul><p>Hey everyone,<br />is there anything we can do in this scenario? We have this problem with a ELTS installation as well. SLES MariaDB 10.2 and PHP 7.2.<br />Are there any other known problems with MariaDB 10.2 and TYPO3 8.7? I am thinking about building a workaround into the install tool for this exact case, has anyone done this before?</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4330782020-10-10T00:36:38ZYurii Panchenko
<ul></ul><p>Tim Spiekerkötter wrote:</p>
<blockquote>
<p>Hey everyone,<br />is there anything we can do in this scenario? We have this problem with a ELTS installation as well. SLES MariaDB 10.2 and PHP 7.2.<br />Are there any other known problems with MariaDB 10.2 and TYPO3 8.7? I am thinking about building a workaround into the install tool for this exact case, has anyone done this before?</p>
</blockquote>
<p>I was migrating the database to typo3 v10 (php7.4, mysql 5.7). I had an error with the field:</p>
<p>`seo_title` varchar (255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ',<br />I did this and the error went away:<br />1) Made a new empty field<br />`seo_title_temp` varchar (255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ',<br />2) Copied information excluding NULL<br />UPDATE `pages` SET `seo_title_temp` = `seo_title` WHERE `seo_title` IS NOT NULL<br />3) Removed `seo_title`<br />4) Renamed `seo_title_temp` to `seo_title`</p>
<p>There is no more error)))</p> TYPO3 Core - Bug #82023: Install Tool DB Analyzer tries to change all VARCHAR fieldshttp://forge.typo3.org/issues/82023?journal_id=4397332021-02-12T12:19:44ZTomas Norre Mikkelsen
<ul></ul><p>I'm facing this issue with:</p>
<p>TYPO3 8.7 ELTS<br />MariaDB: 10.1.x<br />PHP: 7.2.x</p>