mmmm Jom, just how much data do you have in the database that you are trying to pull back in a single query?
It doesn't really matter *how* the data is transferred from the database to the web application; if you do "select * from table" with no limit or paging on it, then thats just sloppy coding, and not the fault of the OpenBD or any application server; its merely trying to do what the developer asked it to do. jomlian wrote: > This may be the problem (mysql) but only the openbd or farcry guys > could answer this one; Jom > > ResultSet > > By default, ResultSets are completely retrieved and stored in memory. > In most cases this is the most efficient way to operate, and due to > the design of the MySQL network protocol is easier to implement. If > you are working with ResultSets that have a large number of rows or <snip> --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official blog @ http://blog.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
