> Had you thought about using a single SQL statement to populate > everything? In other words, if your cycle is: > - Get a bunch of user response objects > - For each user response object, get its user feedback objects > This is something which is very easy to do with two SQL statements, > rather than one plus one per user response object. Since there's > overhead in each SQL Statement you issue, a good place to start might be > in doing this.
It's actually a little more complex than that. What happens is that I perform a number of calculations, which use variables stored in the database and depending on the result more information is retrieved from the database and added to the response. It's not a standard 1-n or n-n relationship, but more extracting data on the fly. One option is to store the calculation variables in a hash table stored in application scope and only change them when they have been updated. Will using something like iBatis or even Hibernate improve the situation? Zoran --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
