dbi buffers results before returning?
From the perl dbi I'm doing a 'SELECT * FROM table' on a table with about 14M rows.
I noticed that the perl processes memory footprint gets huge. It seems that mysqld starts streaming results to perl immediately. The perl dbi buffers all rows in memory. Only once all rows in the result are received will $sth->execute() return and allow me to start processing rows. Any way to get perl to return from $sth->execute() and still receive rows from mysql? I guess I was hoping for a multithreaded implementation of the perl dbi (I know perl's not great with threads).
If perl can't do this well would anyone recommends a different language/dbc engine to use that could return results while still receiving results from mysql? Is there a better way to do this in perl?
Thanks,
Tait
Subject
Written By
Posted
dbi buffers results before returning?
November 09, 2006 02:58PM
November 10, 2006 04:29AM
November 10, 2006 10:34AM
November 15, 2006 03:18PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.