Spring Tips: the Jetbrains Exposed ORM for Kotlin

Hi, Spring fans! In this installment we look at the Exposed Object Relational Mapper framework for Kotlin. #Kotlin #Java #JDBC #springboot #jetbrains

[@andromadusnaruto1544]

Awesome. I'm glad Exposed is getting more light. I've been using it in Spring Boot as a replacement for Spring JPA/Hibernate.

[@antonlakida7999]

you can simplify by naming the lambda parameter explicitly, rather than doing in inside of the lambda: forEach { name -> ...} instead of forEach { val name = it ...}

[@AntonArhipov]

JetBrains - capital 'B' 🙏

[@NealeUpstone]

Any response on the GraalVM hints issue raised?

[@AntonArhipov]

@@NealeUpstone, as I understand, the solution for GraalVM is there: it needs metadata configuration, either as hints or as an external configuration collected via profiling runs. As the issue isn't closed, the team is still looking into that

[@LuisTrigueiros]

Thank you it great, do you have the gist so that I can try to reply it in my end

[@landsman737]

Interesting1

[@jhcao23]

Can next one talk about Exposed with coroutine?

[@mounirboussetta]

How is this Exposed compared to JdbcClient?

[@zombi1034]

JdbcClient is not an ORM so they don’t really compare. JdbcClient has a simpler and nicer to use interface than the older JdbcTemplate api. You still have to write your sql queries manually, whereas an ORM maps directly from Java (or Kotlin) objects to database entries/queries.

[@mohammedhewedy8231]

I think you trimming too much of the video. IMHO, better not to do so, so the viewer can't get lost in the middle

[@GakisStylianos]

Which part was trimmed?