Open
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
1 participant
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.
I was bulk loading a bunch of records that started with zero ("0f1c7a00-b0c3-11df-bedb-003048c3cf84") and then reindexing them with rake sunspot:solr:reindex . If ALL of the records started with zero the reindex would fail because records.last would be nil and the call to records.last.id would fail.
If only some of the records started with zero, they would get skipped and not indexed.
The change doesn't break integer ids because if integers are being used the string Zero will be converted and compared as a number by the database itself (at least for mysql, postgre, sql server and oracle).