Actions
Bug #90751
closed
database compare shows differences for fresh installation
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2020-03-12
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
having a fresh v10 current master installation with sqlite database shows schema differences in the compare database function of the install tool.
This should not happen.
Analysis reveals that the uid column is reported to be a primary key and of type "signed", whereas the default TCA schema suggests to not create a primary key for sqlite and making the uid an "unsigned" integer.
The primary key exception for sqlite was added with #86490.
So far it seems that sqlite reports the uid field as PRIMARY KEY even though it was not created like this.
Updated by 
Updated by 
Updated by
Actions