[BUGFIX] Use the doctrine type instead of binding type in DataSet
#691
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change uses the doctrine type instead of the type
bindingtype in
DataSet->import()still ensuring thatthe value is encoded with current implementation within
the TYPO3 Connection, while preparing to remove custom
handling and using Doctrine DBAL behavour. With this
modification both code paths are working.
Additionally, the columnname is now used for the created
types array effectly fixing a bug that this information
has not been used and fallback to database schema was
used anyway.
Releases: main, 9, 8