Project

General

Profile

Actions

Bug #54917

closed

Debug "Column 'first' cannot be null"

Added by Thomas Skierlo over 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Indexed Search
Target version:
-
Start date:
2014-01-12
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
no-brainer
Is Regression:
Yes
Sprint Focus:

Description

On current master TYPO3 6.2.0beta3 I'm getting this debug message in FE (if in development mode). Fresh install, no upgrade.

exec_INSERTquery
caller     TYPO3\CMS\Core\Database\DatabaseConnection::exec_INSERTquery
ERROR     Column 'first' cannot be null
lastBuiltQuery     INSERT INTO index_rel (phash,wid,count,first,freq,flags) VALUES ('260439973','17213122','1',NULL,'1126.7605633803','128')
debug_backtrace     require(24/typo3/sysext/cms/tslib/index_ts.php),24/index.php#41 // TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->generatePage_postProcessing#207 // TYPO3\CMS\IndexedSearch\Indexer->hook_indexContent#3368 // TYPO3\CMS\IndexedSearch\Indexer->indexTypo3PageContent#309 // TYPO3\CMS\IndexedSearch\Indexer->submitWords#574 // TYPO3\CMS\Core\Database\DatabaseConnection->exec_INSERTquery#2021 // TYPO3\CMS\Core\Database\DatabaseConnection->debug#198

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #53662: DatabaseConnection INSERTquery does not allow NULL valuesClosed2013-11-15

Actions
Actions

Also available in: Atom PDF