Hi there! Want to drop in and say that I've enjoye...

# exposed

[Yang Wang]

Hi there!
Want to drop in and say that I've enjoyed using Exposed DAO and DSL over the last year. I particularly love the ease of use of Exposed DAO, and how it makes mapping relationships to objects easier.

However, my team thinks Exposed DAO is confusing because of the weird caching mechanism in wrapRow() , which may return stale value and cause bugs. So they are going with just Exposed DSL and map to Kotlin data classes instead.

I'm not ready to move away from Exposed DAO yet, so would appreciate if you can help look into this issue. I managed to reproduce the wrapRow issue we ran into in a test and linked a PR in Youtrack.

Thanks!

[e5l]

Hey, thanks! I will take a look