Handle non-standard schemas when looking up identity column #1436
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current MSSQL implementation fails to find Identity columns in non-dbo schemas.
In list-all-columns.sql the query uses
which limits the scope of the object query to the primary schema (dbo). Thus, when using an alternative schema the IsIdentity column always returns null.
The fix is to include the schema when querying for object_id which will work for both primary and secondary schemas.