Kazuhiro Sera

Indeed, it's a little bit confusing but you need to use `#column` instead for insert/update/delete SQLs instead. http://scalikejdbc.org/documentation/query-dsl.html#delete

Introducing some kind of "marked" SQLSyntax may improve type safety of the APIs but it would bring backward incompatibility. It might be considerable in 3.0 (no plan yet though)

Indeed, `java.time.*` values should be supported.

ParameterBinder works also for the query logging. But in this case, just having more patterns here https://github.com/scalikejdbc/scalikejdbc/blob/1518c1a54bfe2182843208bec38e0438b3010a68/scalikejdbc-core/src/main/scala/scalikejdbc/StatementExecutor.scala#L50-L70 would be enough.

Ah, I see. `Binders` can be a `ParameterBinderFactory`. But it's not a `ParameterBinder`. Thus, in this case, the logging doesn't work with it properly. You're right. And unfortunately, I don't...

How about doing like this? ~~blog.seratch.net/post/76689657956/how-to-extend-scalikejdbc-querydsl~~ (this URL is no longer available)

@sjurco Sorry for my belated reply. The solution you suggested looks fine. I welcome your pull requests to enable the new way.

Having a global setting for it may be okay. However, I am not willing to have it so far. If you're using MySQL / PostgreSQL, both of them support socketTimeout...

I see. Fair enough.

If we have the setting globally, having it per a connection pool would be straight-forward. I have one concern about the possible implementation. `ConnectionPoolSettings` already has `connectionTimeoutMillis` to set timeout...