Re: ClojureQL confusion: getting a hold of the results

2009-08-12 Thread Meikel Brandmeyer
Hi, On Aug 12, 11:43 am, Maximilian Karasz wrote: > May i ask what kinds of improvements are planned for connection handling? > Do you want to move it into the direction of persistent connections / > connection pools? We are currently looking into ways the user might specify connections himsel

Re: ClojureQL confusion: getting a hold of the results

2009-08-12 Thread Maximilian Karasz
Hi, On Tue, Aug 11, 2009 at 10:22 PM, Meikel Brandmeyer wrote: Yes. run uses a one-shot connection. When you leave the body > the connection will be closed. Hence the second form cannot > work, because the connection is already closed. We are currently > working on improving the connection handl

Re: ClojureQL confusion: getting a hold of the results

2009-08-11 Thread Meikel Brandmeyer
Hi, Am 11.08.2009 um 21:59 schrieb Maximilian Karasz: ah, thank you so much for the hint, forcing the sequence did the trick. out of curiousity: while the following works (cql/run [*connection* result] (cql/query * people) (doall (take 5 result))) this does not (doall (cql/run [*connec

Re: ClojureQL confusion: getting a hold of the results

2009-08-11 Thread Maximilian Karasz
ah, thank you so much for the hint, forcing the sequence did the trick. out of curiousity: while the following works (cql/run [*connection* result] (cql/query * people) (doall (take 5 result))) this does not (doall (cql/run [*connection* result] (cql/query * people) (take 5 result))) suggestin

Re: ClojureQL confusion: getting a hold of the results

2009-08-11 Thread Christopher Wilson
It looks like (speaking without having looked at the ClojureQL source) the results are being returned as a lazy sequence. In the first case the sequence isn't being realized but it is in the second. On Tue, Aug 11, 2009 at 2:15 PM, Maximilian Karasz wrote: > Hi, > > i've been wanting to play wit