can you recommend other orm ?

Have you tried https://github.com/JetBrains/Exposed ?

if u ask in the #relational-sql channel, u'll get better answers about orm

Ok thanks

Oh, have you tried https://github.com/Kotlin/ktor ?

not sure how complex ur db needs are - for example postgresql jsonb, etc. the #relational-sql will help according to ur specific usecase

no - ktor is interesting, but i havent tried it

Thanks for reply

@tadas44 I don't see why you can't use Dagger2 on the server-side as well, if you want to. I have used it successfully on a server-side project as a simpler (and more performant) alternative to Guice and #spring . (cc: @miha-x64 )

And yeah, IMO stay away from heavy-weight ORMs light Hibernate... go with something like JOOQ or QueryDSL to maintain query type safety, but keep all the expressiveness of SQL. If you're brave, you could try @orangy 's new type-safe SQL project, Squash: https://bintray.com/kotlin/squash/squash.

@rocketraman why is hibernate considered a "heavy-weight" ORM? From experience trying many different ORMs, Hibernate is the most complete ORM solution out there with the widest support for different databases. You also get to write in native SQL if you really need to, HQL (which is my preferred way of doing it) or do it the JOOQ way.

@janvladimirmostert I think its not hard to see why it's "heavy-weight" 🙂 Just look at its documentation, and the SQLs it generates. I'd bet dollars to donuts if you tried to integrate immutable data classes and Hibernate you'd fail miserably, or be saddled with some ugly workarounds... Having used Hibernate extensively in the past, as well as projects like Jooq, QueryDSL, and Spring Data as counterpoints, I would always think twice before using Hibernate again. IMO, the tradeoffs it requires aren't worth it.

@rocketraman I can see why immutable data-classes would be useful for data read from the DB, but that's not a deal-breaker for me:

@Entity
@Table(name = "Companies")
@JsonIgnoreProperties(ignoreUnknown = true)
class Company(

	@Column(unique = true)
	var name: String = ""

) : StandardEntity() {

	fun getCompanyByName(em: EntityManager, name: String): Company {
		val query = em.createQuery("SELECT o FROM Company AS o WHERE o.name=:name", Company::class.java)
		query.setParameter("name", name)
		return query.singleResult
	}
}

Superclass:

@MappedSuperclass
open class StandardEntity {

	@Id
	@GeneratedValue(strategy = javax.persistence.GenerationType.AUTO)
	@Column(name = "id")
	var id: Int? = null

	@Version
	@JsonIgnore
	@Column(name = "version")
	private var version: Int = 0
  ....
}

If hibernate is used properly, queries are also optimal in the majority of cases, if you need something that is much better optimised, there's always the option of native queries. I've used JOOQ and SpringData, Torque, and several other ORMs, Hibernate suits my needs much better. JOOQ actually charges you a license fee if using SQLServer / Oracle DBs, some clients actually use those, so with Hibernate, write in MySQL and just switch to their DBs.

@rocketraman thanks for pointing out

squash

. Maybe you could recommend rest api framework?

I heard that

vertx

is great, what else?

@tadas44 I've used VertX's "database layer", if you enjoy writing native, that'll be a perfect fit for you. It's using C3P0 under the bonnet and a threadpool, so a pretty decent setup out fo the box

I want fancy stuff like RxJava out of the box 😄

No database abstraction layer offers that at the moment

I think there's an experimental Scala one that does, we discussed this in depth in #relational-sql

I haven’t tried, but from examples it seems it supports Rx

It's probably still blocking under the bonnet just using a thread-pool ?

Ah, I see there's a non-blocking API, looks interesting

I ask guys about this library in #relational-sql channel

Immutable data classes cannot be constructed when there are loops. Loops need 2-phase construction, like create an instance and then populate data separately. In

squash

I’m experimenting with "data interfaces”, and codegen under the hood. Now trying to convert @sdeleuze’s geospatial exposed sample.

@rocketraman I agree with you about Dagger. I thought about Spring with its own

@Autowired

and asked myself “Why we need Dagger there?” But with other frameworks or without them Dagger might be quite handy. I like immutable data classes so much, but are there any benefits from immutable objects with really

final

fields in comparison with effectively-immutable objects that must be initialized e. g. by Hibernate? Scott Oaks, author of "Java Performance: The Definitive Guide” says that despite some myths there is no performance impact from final fields.

Requery.io sounds like what Tadas wants 😀 No fancy caching etc from most orms though.

@tadas44 vertx supports rxjava http://vertx.io/docs/vertx-rx/java/

anyone know what is the status of native kotlin integration in vertx ? I think someone from Jetbeans was working on this

#vertx for more details. They are waiting for some code style fixes, but @cy is busy with other tasks here.