far too magic to check for something that basically isn't trustable: even if you code something like that and you check that there's x mb available, another user can ask for another huge set of data and your "previoulsy" free RAM is not free anymore.
On Wednesday, November 7, 2012 11:59:18 AM UTC+1, Johann Spies wrote: > > On 7 November 2012 12:33, Niphlod <nip...@gmail.com <javascript:>> wrote: > >> woking on 1. >> > > Thanks. > > >> for 2, how do you "foresee" how much time and RAM the present query will >> take to be serialized ? >> > > I don't know. I suspect a possible method would be: > > * Determine the average size of a record calculated on the result of the > present query handled by the grid. > * Determine the available ram on the server > * Calculate the size of the total result. If it is more than say 80% of > the available ram, download in multiple files and warn the user about > it. > * I don't know about the time-out issue. > > An alternative (and easier option) would be to warn the user that the > result is too large to be downloaded in one file and advise him/her to > adapt the query to get the result in smaller portions. > > Regards > Johann > -- > Because experiencing your loyal love is better than life itself, > my lips will praise you. (Psalm 63:3) > > --
