Rick Moynihan

Just run into this issue too: Here's a minimal case: ```clojure ((ataraxy.core/handler { :routes '{[:get "/hello"] ^:af [:hello]} :middleware {:af ring.middleware.anti-forgery/wrap-anti-forgery} :handlers {:hello (fn [req] [:atraxy.response/ok "hello"])}}) {:uri "/hello" :request-method...

It would also be good to get a more complete list of missing features and functionality. Our current approach has been pretty adhoc, and I think it would be good...

`conj-cols` `conj-rows` in incanter (Are they lazy?)

`grep` is now a more general `rows`... makes me think we should also support `grep-columns` - or a better way of selection that lets you grep in either dimension or...

Not a `dataset -> dataset` function but useful for building them is the `dataset -> seq` function: ``` clojure (defn column->seq [ds column] (->> ds :rows (map #(get % column))))...

It might be useful for `build-lookup-table` to accept a default value to return when `:not-found`. It may also be useful for this to be a function, to e.g. return another...

Agreed we should close this, but does this manifest itself as an error or a bug at all? What symptoms does this have?

Nice one @scottlowe, Is the sesame issue fixed in RDF4j? Because if it is it might be worth postponing until we can use an RDF4j grafter build. If it's not...

Ok good explanation @scottlowe, and makes perfect sense about what's happening. If you're looking at testing this with RDF4j you can check by using this branch/ns https://github.com/Swirrl/grafter/blob/0.12.x-SNAPSHOT/src/grafter/rdf4j/sparql.clj That branch should...

Why do you need to access things at this level? Can't you just use the grafter `query` function? http://api.grafter.org/master/grafter.rdf.repository.html#var-query