Hi Stuart,
That fixes the problem, thank you.
When I ran the result-set through (type), it showed me that the
instance was actually a ResultSetStream. While the Jena ResultSet
interface doesn't act as a closable resource, perhaps the stream was
being closed once the owning QueryExecution obj was
Hi,
On Feb 16, 9:55 am, Stuart Halloway wrote:
> map is lazy, count and butlast are not lazy. Does adding a doall
> around your call to map fix this problem?
Argh. butlast is only unlazy of degree one, so to say.
Is there a reason why not to provide a lazy version:
(defn butlast
"Return a
Hi Rob,
map is lazy, count and butlast are not lazy. Does adding a doall
around your call to map fix this problem?
Stu
(map handler (iterator-seq result-set)) always throws a
NoSuchElementException
(map handler (butlast (iterator-seq result-set))) always works.
(count (iterator-seq resu
