# Re: Is there a way to avoid having the library slurp-read th

**URL:** <https://www.ruby-forum.com/t/re-is-there-a-way-to-avoid-having-the-library-slurp-read-th/101372>\
**Category:** Ruby\
**Created:** [August 4, 2006, 4:06pm UTC](https://www.ruby-forum.com/t/re-is-there-a-way-to-avoid-having-the-library-slurp-read-th/101372 "2006-08-04T16:06:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kivle](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/e480ec/32.png) [@kivle](https://www.ruby-forum.com/u/kivle)\
**Post date:** [August 4, 2006, 4:06pm UTC](https://www.ruby-forum.com/t/re-is-there-a-way-to-avoid-having-the-library-slurp-read-th/101372/1 "2006-08-04T16:06:23Z")

</div>

Yep, that’s pretty much what I’ve found. The suggestion by Depesz to use  
cursors worked wonderfully though. Basically you wrap it up in a  
transaction on the server side, and the cursor gives you x amount of  
rows at a time when you request it. 1000 rows slurp-read is quite a bit  
less resource intensive than 2 million. 😉

Helge