Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Adding is_filtered_index for SQL Server dialect
See original GitHub issueI noticed that SQLAlchemy does not reflect the filter definition of SQL Server indexes. I see how this makes sense since you expect the filter definition to be a SQLAlchemy construct instead of a SQL string.
https://docs.sqlalchemy.org/en/13/dialects/mssql.html#filtered-indexes
However, it is not possible to determine if a unique index implies uniqueness in a subset of the table or the entire table without this information. Would be possible to add an is_filtered_index dialect-specific kwarg for MSSQL Server or something along these lines? I would be happy to implement it and submit a PR.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
hey there.
Can we just augment the first query at the top of def get_indexes() with the extra columns? that way we can just use the query we already have.
RamonWill has proposed a fix for this issue in the master branch:
Add support for SQL Server filtered indexes https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/2142