Skip to content

[TASK] Use the doctrine type instead of binding type in DataSet#690

Merged
sbuerk merged 1 commit intomainfrom
dataset-import
Nov 11, 2025
Merged

[TASK] Use the doctrine type instead of binding type in DataSet#690
sbuerk merged 1 commit intomainfrom
dataset-import

Conversation

@sbuerk
Copy link
Collaborator

@sbuerk sbuerk commented Nov 10, 2025

This change uses the doctrine type instead of the type
bindingtype in DataSet->import() still ensuring that
the 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.

Releases: main, 9, 8

This change uses the doctrine type instead of the type
bindingtype in `DataSet->import()` still ensuring that
the 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
@sbuerk sbuerk merged commit 8374c8e into main Nov 11, 2025
8 checks passed
@sbuerk sbuerk deleted the dataset-import branch November 11, 2025 08:54
reviewtypo3org pushed a commit to TYPO3/typo3 that referenced this pull request Nov 11, 2025
Update `typo3/testing-framework` to have required
code in place working with changes in extbase and
TYPO3 Connection.

Command(s):

**main**
> composer u 'typo3/testing-framework

**13.4**
> composer req --dev 'typo3/testing-framework':'^9.2.1'

**12.4**
> composer req --dev 'typo3/testing-framework':'^8.3.0'

[1] TYPO3/testing-framework#690
[2] TYPO3/testing-framework#691

Resolves: #108039
Releases: main, 13.4, 12.4
Change-Id: I47c3b95b85a4940b1b034dbbd033cb868e01f5ba
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/91483
Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Oliver Klee <typo3-coding@oliverklee.de>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
reviewtypo3org pushed a commit to TYPO3/typo3 that referenced this pull request Nov 11, 2025
Update `typo3/testing-framework` to have required
code in place working with changes in extbase and
TYPO3 Connection.

Command(s):

**main**
> composer u 'typo3/testing-framework

**13.4**
> composer req --dev 'typo3/testing-framework':'^9.2.1'

**12.4**
> composer req --dev 'typo3/testing-framework':'^8.3.0'

[1] TYPO3/testing-framework#690
[2] TYPO3/testing-framework#691

Resolves: #108039
Releases: main, 13.4, 12.4
Change-Id: I47c3b95b85a4940b1b034dbbd033cb868e01f5ba
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/91558
Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
reviewtypo3org pushed a commit to TYPO3/typo3 that referenced this pull request Nov 11, 2025
Update `typo3/testing-framework` to have required
code in place working with changes in extbase and
TYPO3 Connection.

Command(s):

**main**
> composer u 'typo3/testing-framework

**13.4**
> composer req --dev 'typo3/testing-framework':'^9.2.1'

**12.4**
> composer req --dev 'typo3/testing-framework':'^8.3.1'

[1] TYPO3/testing-framework#690
[2] TYPO3/testing-framework#691

Resolves: #108039
Releases: main, 13.4, 12.4
Change-Id: I47c3b95b85a4940b1b034dbbd033cb868e01f5ba
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/91559
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Tested-by: Oliver Klee <typo3-coding@oliverklee.de>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
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.

2 participants