> I owe u a cold one for that...50% less memory usage. :-)
It only has to hold the query resultset in RAM, not the page
anymore. If you like digging into java and your database supports
it, using a cursor will reduce the RAM usage further.
** Gotcha
> In the case where I'm emailing a CSV, I don't imagine there's much I
can
> do...(hope I'm wrong)
> I originally had it looping over CFFILE but it was painfully slow...I
> guess with the large number of file I/O's...this one stores in request
> and makes single cffile dump at the end.
Using java.io.* might make it faster.
** Possibly, but considering most users opt for the download, and only
in edge cases are the recordsets large, I'll claim victory and call it a
day. ;)
If your database is local and supports it you might be able to
use the database to write a .csv.
** We're limiting the starin of any reporting on this particular DB.
It's massive but it's primarily for OLTP, schema is icky for reporting.
(Although we're trying out some materialized views.
** Thanks 4 help!!
Jochem
________________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
