New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iterator support #1087

Open
jethrogb opened this Issue Aug 10, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@jethrogb
Contributor

jethrogb commented Aug 10, 2017

I'd like to issue select queries that return all data lazily in the form of an iterator. I want to issue queries for a million rows or so and I don't want to allocate all the memory up front.

This seems to have been the way things worked, but it was changed in #132/#142. I don't fully understand the rationale for the change. I also don't care about associations for this particular query.

@vandenoever

This comment has been minimized.

Show comment
Hide comment
@vandenoever

vandenoever Nov 26, 2017

I'd very much appreciate the convenience of ORM without the memory allocation overhead. An iterator that returns shallow items that use &str instead of String would be good in low-memory use-cases.

vandenoever commented Nov 26, 2017

I'd very much appreciate the convenience of ORM without the memory allocation overhead. An iterator that returns shallow items that use &str instead of String would be good in low-memory use-cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment