gatling-jdbc VS ScalikeJDBC

Depending on how adventurous you're feeling, you can extend Gatling's functionality pretty easily. Here's an example I found where someone does this for JDBC. In particular you might want to take a look at JdbcInsertAction and JdbcInsertionActionBuilder, and then the log function here.

You can also try http://scalikejdbc.org which is my personal favorite.

Maybe not what you're looking for but ScalikeJDBC is published for Scala 3 since version 4.0.0.

I have had poor experiences with "fancy" SQL libraries in multiple languages when I go past basic operations. This includes Slick and Quill in Scala.

I don't remember what the problems were with Slick that leave such a bad feeling when I hear its name -- that was 5 years ago -- but I had problems with Quill just last year. I was trying to use it to generate an efficient "in" query against a two column composite primary key, and nothing seemed to work. Since it uses macro magic, one of my attempts triggered an internal compiler error instead of normal compiler feedback.

I ended up dropping Quill for ScalikeJDBC:

http://scalikejdbc.org/

It seems to be less popular/active than other libraries, but it is dead simple to use, even for developers new to Scala. I write exactly the SQL I want just like I would in psql. There is little-to-no magic [1]. I think that the only slightly magical feature I use is ensure that variable interpolation into SQL ("SQLInterpolation") prevents injection attacks.

[1] It actually has capabilities to automatically map tables/columns into different structures and generate code for you, but my team doesn't use any of that. We just write SQL.