I've just tried the lib `Iciql` on a Kotlin projec...
# exposed
h
I've just tried the lib
Iciql
on a Kotlin project but it has 2 issues that I think it is not very good and not suitable for a Kotlin project: 1. The idea of creating an object just to be used as
alias
so that the lib can somehow infer the column name/info: don't really like this, my table-schema don't change that often and once it changes, a bunch of related thing changed as well (business logic linked to the schema change), leading to obvious rebuild 2. The design of NestedCondition.And and NestedCondition.Or seems to be geared toward the java way of using it (I think it is call object initialization), which I cannot translated to Kotlin