in reply to Re^4: Forking and shelling out to curl
in thread Forking and shelling out to curl

Yes, I was full pathing everything. I have access to a RHEL 7 server with a bunch of modules avaialble to me, so I'm using REST::Client, though I just found out it doesn't page data, so I;m back to hitting my head against a wall! :/

Elda Taluta; Sarks Sark; Ark Arks
My deviantART gallery

Replies are listed 'Best First'.
Re^6: Forking and shelling out to curl
by Anonymous Monk on Jan 11, 2020 at 07:50 UTC

    REST::Client, though I just found out it doesn't page data, so I;m back to hitting my head against a wall! :/

    Hi,

    DBI doesn't page data either :) think about it

      DBI can (somewhat) page data, but of course you can only page forward. The following code fetches the results in batches of 10k rows:

      my $rows = []; # cache for batches of rows while( my $row = ( shift(@$rows) || # get row from cache, or reload +cache: shift(@{$rows=$sth->fetchall_arrayref(undef,10_00 +0)||[]}) ) ) { # do processing of row here ... }

      Of course, just because you're transferring the data from the DB driver to Perl space in batches of 10k doesn't mean that the database driver doesn't fetch all available rows onto your machine already.

      Data::Stream::Bulk wraps this approach in an(other) API, but I never got warm with it.