exposed

To set up Kotlin Exposed with HikariCP, configure Database.connect with a HikariCP DataSource, then wrap database operations in transaction blocks. For coroutine integration, use newSuspendedTransaction to manage transactional boundaries within suspend functions.

Exposed module selection depends on your use case: include exposed-core for basics, exposed-jdbc for blocking drivers, exposed-r2dbc for reactive access, exposed-dao for entity lifecycles, and exposed-java-time or exposed-json for specific data type support.

Yes, Kotlin Exposed works with Spring Boot integration using dedicated starters. This skill guides configuring Exposed alongside Spring Boot, handling transaction boundaries and testing considerations for robust application setup.

Define tables in Kotlin Exposed using IntIdTable or LongIdTable classes with column definitions, then map DAO entities by extending Entity classes. This skill covers table and column definitions alongside DAO entity lifecycle management for structured database access.

The transaction function executes blocking database operations synchronously, while newSuspendedTransaction integrates with Kotlin coroutines to handle database operations in suspendable contexts, typically paired with exposed-r2dbc for reactive database workflows.

Kotlin Exposed DSL CRUD operations use select, insert, update, and delete functions. Advanced querying and join patterns are constructed using innerJoin and leftJoin methods to combine multiple tables within a transaction block.