Question 1

next.jdbc vs clojure.java.jdbc performance comparison

Accepted Answer

next.jdbc is designed for better performance with reduced overhead in ResultSet conversion and connection handling, making it faster for large datasets. However, benchmarks vary, and migration is needed to leverage these gains.

Question 2

How to set up connection pooling with next.jdbc

Accepted Answer

next.jdbc relies on external libraries for pooling; use a library like HikariCP to create a DataSource, then pass it to next.jdbc functions. The README mentions this in the usage section but doesn't provide built-in solutions.

Question 3

How to use datafy and nav with next.jdbc results

Accepted Answer

Results from execute! and execute-one! are automatically Datafiable, so you can use tools like Portal or Reveal to navigate them. The datafy/nav support is built-in, as highlighted in the features.

Question 4

Does next.jdbc support transactions

Accepted Answer

Yes, it provides transact and with-transaction for handling transactions, with options for rollback on errors. This is covered in the Transactions documentation linked in the README.

Question 5

How to migrate from clojure.java.jdbc to next.jdbc

Accepted Answer

Start with the migration guide on cljdoc; key changes include adapting to plan, execute!, and qualified keywords. The next.jdbc.sql namespace offers similar syntactic sugar functions to ease the transition.

Question 6

Is next.jdbc good for high-concurrency apps

Accepted Answer

With proper connection pooling, yes—its performance optimizations and protocol design make it efficient. However, you must manage connections carefully, as it doesn't handle pooling natively.

next.jdbc

What is next.jdbc?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions