Bug #81341: recursive is a reserved keyword in MariaDB 10.2. Causes errors in queries for tt_content... - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (2)

Jan Slusarczyk
Markus Klein

Actions

Copy link

Bug #81341

closed

recursive is a reserved keyword in MariaDB 10.2. Causes errors in queries for tt_content...

Added by Jan Slusarczyk almost 7 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Could have

Assignee:

Morton Jonuschat

Category:

Database API (Doctrine DBAL)

Target version:

Start date:

2017-05-25

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

PHP Version:

Tags:

mariadb 10.2,recursive,tt_content

Complexity:

Is Regression:

Sprint Focus:

Description

I have stumbled upon strange errors after upgrading MariaDB to 10.2.6 (stable). Errors where in queries for tt_content table, always when the query contains "recursive" column. I have filed a bug report and got an answer that recursive is a reserved keyword and needs to be in backticks to work properly:

https://jira.mariadb.org/browse/MDEV-12918?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=95783#comment-95783

I don't know if it works the same in 8LTS. I am using 7.6LTS

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Task #83414: Investigate MariaDB 10.2-support for 8 LTS

Rejected

2017-12-22

Actions

Has duplicate TYPO3 Core - Bug #81388: SQL-keyword "recursive" not enclosed in ticks - inserts into tt_content fail with MariaDB >=10.2

Rejected

Morton Jonuschat

2017-05-31

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Morton Jonuschat almost 7 years ago

Category set to Database API (Doctrine DBAL)
Status changed from New to Rejected
Assignee set to Morton Jonuschat
Priority changed from Must have to Could have

This should be fixed on TYPO3 v8 as we replaced the whole database abstraction layer which gave us such things as quoting field names in all queries.

TYPO3 7LTS is now in priority bugfix mode and while we strive to support alternative MySQL implementations like MariaDB or Percona the fact remains that MariaDB 10.2 is feature-wise closer to MySQL 8.0 than to 5.7 (MySQL 8.0 like MariaDB 10.2 gained recursive common table expressions where the new protected keyword comes from).

Given that MySQL 8.0 is not a supported database platform either and that fixing this on TYPO3 7LTS is almost impossible with the existing database architecture in 7LTS classifying this as a must-fix breakage is not warranted.

Feel free to reopen this issue or create a new one if you see the same problems with MariaDB 10.2 or MySQL 8.0 on TYPO 8LTS - we have a much higher chance of fixing it there due to the modernized database layer.

Actions

Copy link

Updated by Morton Jonuschat almost 7 years ago

Has duplicate Bug #81388: SQL-keyword "recursive" not enclosed in ticks - inserts into tt_content fail with MariaDB >=10.2 added

Actions

Copy link

Updated by Morton Jonuschat almost 7 years ago

Related to Bug #76265: Access module - pages with character like "è" in title has not title visible. added

Actions

Copy link

Updated by Morton Jonuschat almost 7 years ago

Related to deleted (Bug #76265: Access module - pages with character like "è" in title has not title visible.)

Actions

Copy link

Updated by Markus Klein almost 7 years ago

Status changed from Rejected to New

Affected users: Mac with mariadb from homebrew

Possible (dirty) fix in v7:
run through the fields to insert/update in TYPO3_DB and quote them (or just the recursive word).

General thing. The core must validate the DB server version it talks to. If MariaDB 10.2 is like MySQL 8 it has to complain.

Actions

Copy link

Updated by Markus Klein almost 7 years ago

The current version check is only:

$minimumMysqlVersion = '5.5.0';
if (version_compare($currentMysqlVersion, $minimumMysqlVersion) < 0) {

So no upper limit is checked.

MariaDB reports: 10.2.6-MariaDB

Actions

Copy link

Updated by Gerrit Code Review almost 7 years ago

Status changed from New to Under Review

Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53148

Actions

Copy link

Updated by Gerrit Code Review almost 7 years ago

Patch set 2 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53148

Actions

Copy link

Updated by Gerrit Code Review almost 7 years ago

Patch set 3 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53148

Actions

Copy link

#10