Join on an Aggregated Sub-Query — Keeping Row-Types Safe with ExoQuery (vs. Exposed)

If you’ve ever tried joining on an aggregated sub-query in Kotlin’s Exposed DSL, you already know the pain — QueryAlias throws away your types and one small mistake blows up at runtime.

This short, inspired by a real Stack Overflow question:
https://github.com/JetBrains/Exposed/issues/1294

With ExoQuery:
✅ The sub-query stays a real SqlQuery — row-types survive every hop
⚡ Safer refactors and compiler-checked joins
🔍 Lean SQL generated under the hood — no manual aliases, no runtime surprises

Watch the demo to see exactly what’s going on, and subscribe to the #ExoQuery30in30 series — one short every day for 30 days. Have a crazy query of your own? Drop it in the comments and let’s simplify it together!

#Kotlin #ExoQuery #Database #DevTips #TypeSafety

Видео Join on an Aggregated Sub-Query — Keeping Row-Types Safe with ExoQuery (vs. Exposed) канала Alexander Ioffe