vincent rogier wrote: > But let's forget Oracle case for now. If you've got a big resultset > (let's say 1.000.000 rows) that has 20 columns with some string based > columns (let's say 3.000 bytes per row). > Actual implementation of libdbi allocates memory for all resultset rows. > With this example, it makes 3Go that have to be allocated !!! Just to > fetch a query... with ocilib, for example, by default, only 60Ko would > be allocated...
Shouldn't you be using cursors when you have result sets of this size? I am no SQL expert, but I saved huge amounts of memory when I started using cursors in a setting like this. But then again, maybe this would not have been necessary if libdbi worked differently. -- --Kjell ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libdbi-drivers-devel mailing list Libdbi-drivers-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
