Bug #54917
Debug "Column 'first' cannot be null"
| Status: | Resolved | Start date: | 2014-01-12 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 100% |
|
| Category: | Indexed Search | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 6.2 | Is Regression: | Yes | |
| PHP Version: | 5.3 | Sprint Focus: | ||
| Complexity: | no-brainer |
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
Associated revisions
[BUGFIX] Indexer tries to insert NULL into DB
The Indexer of indexed_search tries to insert NULL values
into NOT NULL columns of the database.
Since #53662 NULL values are passed to the database,
hence these insert statements now fail.
Resolves: #54917
Releases: 6.2
Change-Id: Ia935abe14b9c3be2062f1b38ec98fb63921a1c2f
Reviewed-on: https://review.typo3.org/26757
Reviewed-by: Georg Ringer
Tested-by: Georg Ringer
[BUGFIX] Indexer tries to insert NULL into DB
The Indexer of indexed_search tries to insert NULL values
into NOT NULL columns of the database.
Since #53662 NULL values are passed to the database,
hence these insert statements now fail.
Resolves: #54917
Releases: 6.2, 6.1, 6.0
Change-Id: Ia935abe14b9c3be2062f1b38ec98fb63921a1c2f
Reviewed-on: https://review.typo3.org/30244
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader
[BUGFIX] Indexer tries to insert NULL into DB
The Indexer of indexed_search tries to insert NULL values
into NOT NULL columns of the database.
Since #53662 NULL values are passed to the database,
hence these insert statements now fail.
Resolves: #54917
Releases: 6.2, 6.1, 6.0
Change-Id: Ia935abe14b9c3be2062f1b38ec98fb63921a1c2f
Reviewed-on: https://review.typo3.org/30243
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader
History
#1 Updated by Markus Klein over 1 year ago
- Status changed from New to Accepted
- Priority changed from Should have to Must have
- Complexity set to no-brainer
- Is Regression changed from No to Yes
This is a regression to #53662.
#2 Updated by Gerrit Code Review over 1 year ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/26757
#3 Updated by Markus Klein over 1 year ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset cca2d70043cc3b724f159f7741fc4ae10c3e1cb6.
#4 Updated by Gerrit Code Review about 1 year ago
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_6-0 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/30243
#5 Updated by Gerrit Code Review about 1 year ago
Patch set 1 for branch TYPO3_6-1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/30244
#6 Updated by Markus Klein about 1 year ago
- Status changed from Under Review to Resolved
Applied in changeset e50f6a64348f3253472605c6c7d5cd9217496d82.
#7 Updated by Timotheus Pokorra about 1 year ago
Just as a note, because it took me a while to find this bug report and the solution:
In Typo3 6.1.8, my indexed_search did not show pages where the searched word was part of the title of the page.
I finally found that if I apply this change that fixes this bug, my problem is solved as well.
(I got here by comparing 6.1.8 and 6.1.9, where this bug has been fixed already)