@seancorfield a little feedback: I just moved a personal project from org.clojure/java.jdbc to seancorfield/next.jdbc (https://github.com/manuel-uberti/boodle). Everything went smoothly, so thanks a lot for the great job and docs. 🙂

In about the same category I just open sourced https://github.com/openweb-nl/open-bank-mark witch moved postgres.async -> java.jdbc -> next.jdbc

@gklijs what were the reasons & end results in moving from async to sync with your db-access?

In my case it was important to keep order, so I wasn't really using the async part. I think cpu was pretty high, and performance not so good. But simplicity was the most important reason to move.

thanks for the insights. interesting note on the performance (haven’t used any of the clojure async wrappers myself).

@seancorfield thanks for letting me know this was here! i double checked and indeed i did have that rewrite flag enabled. do any other profiling tools stand out that might be helpful in pinpointing where this extra time is coming from?

i must say i echo your sentiments on jdbc…

I believe when the issue was diagnosed, it was done via some level of query logging in PostgreSQL...

Let me pull up the JIRA ticket for that...

https://dev.clojure.org/jira/browse/JDBC-174

So that's how the MySQL behavior was diagnosed (and, in that case, the version of MariaDB initially in use did not even support the correct option!).

I don't remember how the original user diagnosed it with PostgreSQL but I assume it was at the DB log level. I don't use PG so I can't offer any help there.

That would be the first step: verify whether you're actually getting a single insert or multiple inserts at the DB level.

If you're getting multiple inserts, then maybe you are not specifying the rewrite flag correctly?

Or you're using a version of the DB driver that doesn't support that flag?

ok, makes sense.

There are, unfortunately, so many variables 😞

love it!

Maintaining clojure.java.jdbc (and, now, next.jdbc) for eight years has been a nightmare at times! 🤯

wow. i was wrong about having that flag enabled. good times

time to recaffeinate, clearly

So you now see a single, fast insert @gtzogana?

yessir.

Awesome! 💯

thanks for the insight