@seancorfield that works perfectly, thanks.

Just nitpicking here, I have a query - (helpers/select :id [(sql/call :ST_AsText :location) :sample/location]) which returns - {:sample/id 1, :location "POINT(32.621431 0.291065)"} Is it possible to either return both as namespaced keys or neither as namespaced keys, its just that the destructuring will be little more pretty. Currently this is what I am doing, which is little jarring -

(let [{:keys [location] :cabs/keys [id]} result]
    [location id])

something like this would work: (jdbc/execute-one! @datasource sql {:builder-fn rs/as-unqualified-lower-maps})]

use the builder-fn

https://github.com/seancorfield/next-jdbc/blob/master/doc/result-set-builders.md

@murtaza52 next.jdbc can only qualify column names where the JDBC driver can provide .getTableName -- which is empty for computed columns.

Hi, I’m migrating a small project to next.jdbc and I noticed that query now returns a namespaced hashmap. How do I un-namespace the result?

https://cljdoc.org/d/seancorfield/next.jdbc/1.0.9/doc/migration-from-clojure-java-jdbc#rows-and-result-sets

That whole page is probably worth reading @pablore

(I'd say the whole docs are worth reading if you're just starting to use next.jdbc -- it should answer all your questions, including DB-specific tips & tricks in the friendly SQL functions section)

I'd also strongly recommend using the primary API (`next.jdbc`) where possible and only using next.jdbc.sql as a migration aid for legacy code.

thanks @seancorfield!