Fix for issue of results table not returning data in insert order#20
Open
barneynicholls wants to merge 1 commit intodrumsta:masterfrom
Open
Fix for issue of results table not returning data in insert order#20barneynicholls wants to merge 1 commit intodrumsta:masterfrom
barneynicholls wants to merge 1 commit intodrumsta:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi, I noticed that the insert and identity on/off statements when pulling from a view often got mixed up and would appear randomly within the output.
I identified the issue being the @results table not having a primary key therefore the results wouldn't necessarily be returned in a specific order.
By adding an IDENTITY column then setting that as the Primary Key the issue was resolved.
Thanks for sql it's been a great help :)