Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUGFIX] Do not consider "0" as empty in the CSV DB import #489

Merged
merged 1 commit into from
Aug 12, 2023

Conversation

oliverklee
Copy link
Contributor

A DB column value "0" is a perfectly valid value and should not be considered to be empty.

Particularly, having a "0" value as the first value in a DB row in a CSV file should still allow the DB row to get importet.

(In general, empty() in PHP behaves in mysterious ways and should be avoided in favor of more explicit and human-predicable checks.)

Fixes #488

Releases: main, 7, 6

A DB column value "0" is a perfectly valid value and should not be
considered to be empty.

Particularly, having a "0" value as the first value in a DB row
in a CSV file should still allow the DB row to get importet.

(In general, `empty()` in PHP behaves in mysterious ways and should
be avoided in favor of more explicit and human-predicable checks.)

Fixes TYPO3#488

Releases: main, 7, 6
@lolli42 lolli42 merged commit b6178d6 into TYPO3:main Aug 12, 2023
2 checks passed
@oliverklee oliverklee deleted the bugfix/empty-values branch August 12, 2023 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: DataSet::parseData() disregards valid content due to empty check
2 participants