I’ve recently checked out Kotlin Exposed, looks re...

# getting-started

[yen]

I’ve recently checked out Kotlin Exposed, looks really cool, but feels rather immature at this point.

What’s everyone’s favourite database library?

[spand]

Ours is Exposed. What did you find it lacked?

[robin]

Yep, using Exposed too, it's great so far.

[APXEOLOG]

I'm using Exposed too, but i share your feelings. Anyway, it works out-of-the-box if you don't have some complex queries / table structure

[Dias]

are there any async IO db libraries out there to leverage coroutines better?

[yen]

Exposed doesn’t support e.g. JSON fields or Postgres upserts yet afaik

[yen]

I really like it though. Coming from Python Django, exposed feels a lot leaner and less framework-y

[APXEOLOG]

@yen There is a snippet to add JSON fields (i use it with postgres). I also saw a snippet for upsert, but i didnt managed to adopt it to my project yet

[Saša Šijak]

jooq

[Spike Baylor]

since this thread has already started, for those who use Exposed, do you have a preference on the DSL vs DAO way of using it? or is one more suitable to specific cases?

[spand]

We just use the DSL. Trying out the other end of the spectrum after getting tired of hibernate and the like.

[APXEOLOG]

I'm also using DSL. Don't need 'deep' connections in my current app

[Spike Baylor]

Interesting, I feel like that might be the way I go as well.

[robin]

Also just the DSL. We want all mutations of data clearly defined through repository interfaces, and not allow any code to arbitrarily modify the database records. Also our scopes are narrow enough that automatically updating the data in existing objects is not a concern.