Andrey.Tarashevskiy
Andrey.Tarashevskiy
@harjis , I agree that validation on DSL level will be a nice feature. About `.all()` function: it doesn't require transaction until you start iterating over its result. About `new{}`...
Thank you for a PR. I think it would be better to resolve it in a more generic way for all ExpressionAliases by making a recursive call to `rawToColumnValue` with...
Hi @davydes , it's a normal behavior as the whole `runBlocking` scope is interrupted when the exception is thrown. Please read more about exceptions and coroutines [here](https://kotlinlang.org/docs/reference/coroutines/exception-handling.html) or [here](https://medium.com/androiddevelopers/exceptions-in-coroutines-ce8da1ec060c)
The same here with `newSuspendedTransaction` if you don't provide a specific context it will be executed within current and when failed the whole context execution will be prevented. You could...
No, there is no dialect for HSQLDB in Exposed, but you can implement it and provide us with PR.
How `DISTINCT ON` differs from simple `DISTINCT`?
AFAIU this a per column function, so you can try : ```kotlin class DistinctOn(val expr: Column) : Function(expr.columnType) { override fun toSQL(queryBuilder: QueryBuilder) = "DISTINCT ON (${expr.toSQL(queryBuilder)}) ${expr.toSQL(queryBuilder)}" } ```
You can define your own StringEntityID (and related classes), Exposed doesn't provide them as it not so common case to use string as a primary key. Please look at [UUIDEntity.kt](https://github.com/JetBrains/Exposed/blob/master/exposed-dao/src/main/kotlin/org/jetbrains/exposed/dao/UUIDEntity.kt)...
It's not on the roadmap right now but we could consider it after implementing support for async java drivers.
@lbensaad , sorry, but I don't really have free time to dive into the native world. The problem is that I need to find the native drivers for each database...