Actions
bug #4957
closedMS SQL Server not functional as it does not allow more than 2100 parameters
Start date:
Due date:
% Done:
0%
Estimated time:
Severity:
normal
Found in Version:
Description
... for an SQL statement.
But e.g. the term loading uses >2100 parameters (all uuids) to load all managed data.
We need to find ways to avoid that many parameters, e.g. by splitting queries if SQL Server is database type.
Related issues
Updated by Katja Luther over 8 years ago
- Target version deleted (
Unassigned CDM tickets) - Priority changed from New to Priority13
Updated by Andreas Müller almost 8 years ago
- Target version changed from Release 4.0 to Release 4.1
Updated by Andreas Müller almost 8 years ago
- Target version changed from Release 4.1 to Release 4.2
Updated by Andreas Müller almost 8 years ago
- Target version changed from Release 4.2 to Release 4.3
Updated by Andreas Müller over 7 years ago
- Target version changed from Release 4.3 to Release 4.4
Updated by Andreas Müller over 7 years ago
- Target version changed from Release 4.4 to Release 4.5
Updated by Andreas Müller over 7 years ago
- Target version changed from Release 4.5 to Release 4.6
Updated by Andreas Müller about 7 years ago
- Target version changed from Release 4.6 to Release 4.7
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.7 to Release 4.8
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.8 to Release 4.9
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.9 to Release 4.10
Updated by Andreas Müller over 6 years ago
- Description updated (diff)
- Target version changed from Release 4.10 to Release 4.12
Updated by Andreas Müller over 6 years ago
- Subject changed from SQL Server not functional as it does not allow more than 2100 parameters to MS SQL Server not functional as it does not allow more than 2100 parameters
Updated by Andreas Müller over 6 years ago
- Related to bug #7113: Adapt SQL Server dialect to support all data types added
Updated by Andreas Müller over 6 years ago
- Status changed from New to Closed
- Private changed from Yes to No
This is fixed, but there is another issue with SQL Server: #7113
Actions