Where do I specify/pass the :schema argument as described in https://cljdoc.org/d/seancorfield/next.jdbc/1.0.9/doc/datafy-nav-and-schema?

the results of a query is namespaced with the table-name. is there a way to remove the table namespace and just have the column names?

(jdbc/execute-one! ["SELECT 1"] {:builder-fn next.jdbc.result-set/as-unqualified-arrays}

oh sorry, that’s for arrays, but you can find the other builder fns in that ns

it’s also in the README

I use {:builder-fn rs/as-unqualified-lower-maps}

FYI @sonnyto clojure.java.jdbc used to make column names unique by adding _N to them (`_1`, _2, etc) when there were collisions. next.jdbc does not do that, so if you use unqualified builders, any column conflicts will result in "missing columns" (since it's "just" a hash map). If you use qualified columns -- which I _strongly recommend_ -- then they will remain unique.

Consider select a.*, b.* from table1 a join table 2 b on a.id = b.someid where b.col = ? -- if both table1 and table2 contain id (very likely!), then you will end up with just one :id column in your rows (which will be b.id I expect).

If you use qualified columns, you'll get both :a/id and :b/id.

(I plan to add that as a caveat in both the migration guide and the result set builder section of the docs today)

Any other documentation improvements that folks would like to see, while I'm doing a "documentation Friday"? https://github.com/seancorfield/next-jdbc/commits/master

When migrating from java.jdbc to next.jdbc is there a preferred replacement for the create-table-ddl functions? Should I be using honeysql instead?

create-table-ddl was a pretty poor helper -- you might just as well write it all out as a string.

(jdbc/execute-one! ds ["
create table foo (
  id int auto_increment,
  name varchar(32),
  primary key(id)
) engine=innodb"])

Yeah, it doesn't buy you a whole lot over just rolling it on your own.

One more easy one: How do I convert this java.jdbc connection map {:connection-uri "jdbc:h2:mem:mem_only"} to jdbc.next. I've got {:dbtype "h2" :dbname "mem:mem_only"} but that isn't right. I've tried many of the options at https://github.com/seancorfield/next-jdbc/blob/master/doc/all-the-options.md but no luck. I need to put mem into one of the keys, but not sure which.

@markbastian {:dbtype "h2:mem" :dbname "mem_only"}

See https://cljdoc.org/d/seancorfield/next.jdbc/1.0.9/api/next.jdbc#get-datasource

OK folks, here's a new feature I'm sketching out https://github.com/seancorfield/next-jdbc/commit/b2b7696973e96581450f9997af8b34f60c32bc87 -- the idea is that you can use it for logging (see the test added in that commit) so builder-adapter is a terrible name for it but I'm not sure if logging-adapter is descriptive enough... Suggestions?

builder-hooks ? 🙂