Miles wrote:
> One concern though: Is that results variable a result set or just a > collection of data. If the former, how is the database connection > handled (closing or returning to the pool)? If the latter, how can > large result sets be returned without exhausting memory from a few > queries? That's the one case where I see ESQL winning out. Surely the controller script should handle this too? After calling the template it should clean up the model.
