Actions
Bug #82202
closed
Database Analyzer does not work on MSSQL
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2017-08-25
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
The Database Analyzer does not work on MSSQL because of various errors. It fails adding fields and in comparing state.
Extract:
Database update failed Error: SQLSTATE [42000, 4901]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column. Column 'actiontype' cannot be added to non-empty table 'sys_history' because it does not satisfy these conditions. Database update failed Error: SQLSTATE [42000, 1752]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Column 'actiontype' in table 'sys_history' is invalid for creating a default constraint. SQLSTATE [42000, 1750]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Could not create constraint or index. See previous errors. Database update failed Error: SQLSTATE [42000, 4901]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column. Column 'usertype' cannot be added to non-empty table 'sys_history' because it does not satisfy these conditions. Database update failed Error: SQLSTATE [42000, 1752]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Column 'usertype' in table 'sys_history' is invalid for creating a default constraint. SQLSTATE [42000, 1750]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Could not create constraint or index. See previous errors. Database update failed Error: SQLSTATE [42000, 4901]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column. Column 'filelink_sorting_direction' cannot be added to non-empty table 'tt_content' because it does not satisfy these conditions. Database update failed Error: SQLSTATE [42000, 1752]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Column 'filelink_sorting_direction' in table 'tt_content' is invalid for creating a default constraint. SQLSTATE [42000, 1750]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Could not create constraint or index. See previous errors.
Updated by Susanne Moog about 7 years ago
- Related to Bug #78921: Copying records fails with SQL error without any message added
Updated by Riccardo De Contardi over 6 years ago
- Category set to Database API (Doctrine DBAL)
Updated by Susanne Moog over 4 years ago
- Status changed from New to Closed
Closing for now, whole setup has to be retested with mssql.
Updated by Jan Delius over 3 years ago
Susanne Moog wrote in #note-3:
Closing for now, whole setup has to be retested with mssql.
This issue should not be closed. TYPO3 officially supports the Microsoft SQL Server according to the homepage. Unfortunately, just the Database Analyzer throws countless errors and inapplicable changes.
Updated by Jan Delius over 3 years ago
After a more intensive search, I found an MR in the Doctrine DBAL project that fixes this specific bug. Unfortunately, composer installed version 2.11 for us, but the bugfix exists only since 2.12.x. As soon as we have 2.12 (or 2.13) installed, this error no longer occurs.
https://github.com/doctrine/dbal/pull/4447
Actions