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

WorkspaceVersionRecordsMigration upgrade from v9 or below #10

Open
msmolik opened this issue Jul 2, 2024 · 0 comments
Open

WorkspaceVersionRecordsMigration upgrade from v9 or below #10

msmolik opened this issue Jul 2, 2024 · 0 comments

Comments

@msmolik
Copy link

msmolik commented Jul 2, 2024

The row updater WorkspaceVersionRecordsMigration for v104/DatabaseRowsUpdateWizard does not really delete database entries with t3ver_wsid === 0 and pid -1.
The deleted field gets set to 1 but the record is still present in the database with pid = -1.

So after executing the upgrade wizard, the alter table commands like
ALTER TABLE pages CHANGE pid pid INT UNSIGNED DEFAULT 0 NOT NULL
Current value: pid INT DEFAULT 0 NOT NULL
still won't work, as there are records left with a negative pid.

As I checked in typo3 v10 the upgrade wizard here has its own updateOrDeleteRow method. There these records are hard deleted.
If you have any idea how to solve this, I might be able to help implement it.

Reproduce:
Initial Typo3 below v10 system
Workspace extension enabled
Some versioning records present
Update to Typo3 v12
Run the Wizard Execute database migrations on single rows of TYPO3 10
Afterwards run a DB compare and try to execute the PID INT to UNSIGNED alter statements

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

No branches or pull requests

1 participant