Project

General

Profile

Actions

Bug #56499

closed

SqlParser: Subselect in WHERE not suported

Added by Andreas Fernandez over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2014-03-03
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hello TYPO3 team,

updating the extension list after deleting "1.extensions.xml.gz" and "1.mirrors.xml.gz" results in a catchable fatal error:

PHP Catchable Fatal Error: Argument 1 passed to TYPO3\CMS\Dbal\Database\DatabaseConnection::_quoteWhereClause() must be an array, string given, called in typo3/sysext/dbal/Classes/Database/DatabaseConnection.php on line 1214 and defined in typo3/sysext/dbal/Classes/Database/DatabaseConnection.php line 1702

After some investigation I found out that the error is triggered by the following part:

integer_version=(SELECT MAX("integer_version") FROM "tx_extensionmanager_domain_model_extension"  "b" WHERE   "b"."repository" = 1 AND  "a"."extension_key" = "b"."extension_key") AND repository=1

in typo3/sysext/core/Classes/Database/SqlParser.php in line 1210.

The used regex does not support any subselect in WHERE clause, so the following parse error is triggered:

No operator, but parsing not finished in parseWhereClause()


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #56354: Speed up updating the extension listClosedBenni Mack2014-02-26

Actions
Actions #1

Updated by Mathias Schreiber almost 10 years ago

  • Assignee set to Andreas Fernandez
  • Target version set to 7.3 (Packages)

Congratulations on winning that one ;-)

Actions #2

Updated by Benni Mack over 9 years ago

  • Target version changed from 7.3 (Packages) to 7.4 (Backend)
Actions #3

Updated by Riccardo De Contardi over 9 years ago

  • Status changed from New to Closed

The resolution of the issue #60857 had also solved this, so I close it.

If you experience this issue again, please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF