Bug #90751
Updated by Markus Klein over 4 years ago
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. Making the uid an unsigned int is somehow strange for me as we have autoincrement on that field too. 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.