Project

General

Profile

Actions

Bug #22720

closed

Better debug output for SQL Explain

Added by Xavier Perseguers over 14 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2010-05-26
Due date:
% Done:

0%

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

Description

Implement what was done for RFC #22657 when using DBAL.

This is considered a bug as it is not the same behavior as in Core and as such may be committed, once implemented, to the DBAL_1-1 branch (TYPO3 4.4).
(issue imported from #M14483)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #22657: Better debug output for SQL ExplainClosedSteffen Kamper2010-05-16

Actions
Actions #1

Updated by Steffen Kamper over 14 years ago

Hi Xavier,

the problem mentioned in related TFC isn't the explain output but the exception thrown with DBAL if you fire such query:
$GLOBALS['TYPO3_DB']->exec_INSERTquery('', array('field1' => '789'));

The exception is thrown because table value is empty. Without DBAl you get this error in debug console:
caller t3lib_DB::exec_INSERTquery
ERROR You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(field1) VALUES ('789')' at line 1
lastBuiltQuery INSERT INTO (field1) VALUES ('789')

Actions #2

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • TYPO3 Version set to 4.4
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #3

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then 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