In case it helps, I've also seen this CPU eating problem. I'm using:
REPL-y 0.1.9 Clojure 1.5.1. I don't know what you guys mean by MBP and MBA.
--mark
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
Yes, the Clojure 1.3 doc is wrong. As a new Clojure user, I was pretty
confused for a while.
But after reading this thread I still don't understand why the map behavior
(where 3 and 3.0 are considered different map keys) wasn't considered
incorrect, rather than the = behavior.
Hi Plamen, I don't have any advice to offer but I'm curious why you want to
bind the table and column type info directly onto the result set. If you
associate them in some other way, then you can just use plain maps and
vectors. Are you trying to have less total objects in your API?
--
You
Thanks for explaining Plamen. Yes, it seems very difficult to treat a
database abstraction as a regular Clojure map/vector. FWIW, in writing an
app I think it works well to use SQL queries to return ordinary
maps/vectors which can then be manipulated as usual. But I think you are
doing
