Bug #68602
closed
Epic #68397: Make TYPO3 work with MySQL strict mode
NULL values in records get transformed to FALSE on T3D import
Added by Morton Jonuschat almost 9 years ago.
Updated over 6 years ago.
Category:
Import/Export (T3D)
Description
Given a database record with a NULL value in a column the export file generated will have a XML node like <field index="link" type="NULL"></field> - properly representing the NULL value.
On Import the value gets transformed into a boolean somewhere during the import.
Wondering about this error. With #55082 this was normally fixed. And if you look at the assertion importPagesAndRelatedTtContentWithDifferentImageToExistingData.csv you see that link is asserted NULL.
If I understand this correctly then the test should fail even when not running in MySQL strict mode. The link field in sys_file_reference is defined as "NOT NULL" with a default of '' (empty string). So the conversion of FALSE to '' makes this test pass?
- Status changed from New to In Progress
- Status changed from In Progress 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 http://review.typo3.org/42260
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/42260
- Parent task set to #68397
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Jep, sure, you are right. Pushed a fix for #68810 to adapt the impexp test data.
- Sprint Focus set to On Location Sprint
- Sprint Focus deleted (
On Location Sprint)
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by