Re^4: Forking and shelling out to curl

[bliako]

just for information: LWP::Protocol::Net::Curl interfaces libcurl with LWP methods. So if one has LWP-based script, can switch transparently to libcurl with this module.

btw, your script when daemonizes switches dir to /. Are you using absolute paths for your log and data files?

It would be better if you provided a simplified example script and complete, not fragments.

[Argel]

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! :/

[Anonymous Monk]

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

[Corion]

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.