This project is archived and is in readonly mode.
find_each and find_in_batches assumes that primary key is a number
-
Robert Pankowecki
- Tag changed from active record, find_each, find_in_batches, primary_key, string to active record, find_each, find_in_batches, primary_key, rails3, rails3.0.1, string
-
Denis Odorcic
From the comments:
# It's not possible to set the order. That is automatically set to # ascending on the primary key ("id ASC") to make the batch ordering # work. This also mean that this method only works with integer-based # primary keys. You can't set the limit either, that's used to control # the the batch sizes.Guessing this'll be tagged as a wontfix
-
Robert Pankowecki
Is there any particular reason why this should only work on integer ids ? I see no reason for such restriction.
-
Kane
i agree with robert
-
rails
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
rails
- State changed from open to stale