I had memory problems because cfquery takes the entire
resultset into memory, and this can be a problem when preparing
listings of 100,000+ rows. That is what i started using jdbc, and
it happened to work with cfoutput. Alas, if you dont close the jdbc
connection it will be opened until restart, so remember to include
a try/catch when using this.
The difference is not only by the shorter response time when
using large resultsets. A huge resultset will cause a
java.lang.OutOfMemory exception and sometimes a server crash, when
loaded at once in memory.