JetBrains / JetBrains/Exposed

Kopi and Exposed compatibility

Open
#1,501 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
9.3k
Forks
798
Avg merge
4d 2h
Merged PRs (30d)
26

Description

The framework [Kopi](https://github.com/kopiLeft/Kopi) is similar to Exposed in the way that it runs sql statement inside a transaction and it supports many database dialects.

Inorder to migrate progressively our applications written with Kopi to Exposed, we want to be able to run Exposed statements inside Kopi transactions.

Is it possible to achive this? If yes could you provide some guidelines?

**PS**:
- At the end of the transaction, the kopi transaction performs commit/rollback and closes the connection.
- Kopi transaction can provide java.sql.Connection to Exposed transaction.
- We don't need to have nested transactions.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing Exposed's transaction handling and how it could consume the java.sql.Connection provided by a Kopi transaction. Determine whether Exposed statements can run without nested transactions while Kopi retains responsibility for commit, rollback, and closing the connection; document the compatibility guidance or limitations.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin, sql
Domain
database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.