Yes, I tried, but couldn't believe it :-)

Just thought of JDBC Connections, where you first execute a statement, then call the getResult() method.

With directly calling QueryProcessor.value(), I have just halved the execution time of a query (10 sec to 5 sec, for example).

Thanks!

2013/10/11 Christian Grün <christian.gruen@gmail.com>

> So, calling QueryProcessor.execute() AND after that calling
> QueryProcessor.iter/value() does the work twice?
> I.e., to get the result, I do not need to execute() the query, but instead
> directly call QueryProcessor.iter() or QueryProcessor.value()?

Well, yes… Just try ;)