Which ORM?

[Justin L]

Its been a while since I've created a new Play application.

What is the ORM of choice these days for Java Play apps?

The last time I used eBean. But it looks like it is inactive.

Slick?

anorm + SQL?

I see a link on 2.3 docs to Spring Data?

[Rafael Trindade Chiappetta]

Slick isn't ORM.

=====
Rafael Trindade Chiappetta

http://about.me/rafaeltc

@rafaeltscs

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Justin L]

Neither is anorm. I apologize for any confusion. I am asking how the community chooses to access databases in Java apps written with Play Framework 2.3.x.

[Naftoli Gugenheim]

I think slick and anorm require scala.
From Java I would say to have a look at JOOQ.

[Thiago Lima]

Ebean is not inactive at all. Check their usergroup, here at google groups. https://groups.google.com/forum/#!forum/ebean

[Jamie X]

JOOQ looks really nice, But - like Slick - requires licensing in a commercial environment.

So if you don't have any budget then that might be a consideration.

[Mirco Dotta]

That’s incorrect. You can use Slick for free with all open source databases (see here for a list of supported databases). While, if you are using Oracle, IBM DB2 or Microsoft SQL Server, then usage is free during development, but you’ll need a license for production.

Cheers,

Mirco

----------------

Mirco Dotta - @mircodotta

Typesafe – Build reactive apps!

[Mirco Dotta]

Forgot the link to the list of supported databases :-) Here it is http://slick.typesafe.com/doc/3.0.0-RC1/introduction.html?highlight=databases#supported-database-systems

----------------

Mirco Dotta - @mircodotta

Typesafe – Build reactive apps!

[Rafael Trindade Chiappetta]

grabbing a hook at this question...

talking about scala. would you guys go with Slick or eBean?

=====
Rafael Trindade Chiappetta

http://about.me/rafaeltc

@rafaeltscs

[Pedro Antonio Hidalgo Guzmán]

I prefer Ebean. I use it with java and scala as well.

[Rafael Trindade Chiappetta]

I had some problems using eBean together with specs2.. it was complaining about the entity not being enhanced. I didn't find out any way to solve this, so I switched to slick to give it a try. I think it is nice, but way different. It is not an ORM, so I need to get used to it.

=====
Rafael Trindade Chiappetta

http://about.me/rafaeltc

@rafaeltscs

[Aurélien]

I also advise jOOQ on a Java environment (though it is not an ORM).

However, jOOQ only requires licensing if you are working with commercial databases (ie Oracle, SQL Server, ...). That means that even in a commercial environment, jOOQ is completely free if you are using MySQL or PostgreSQL. To be sure, you can check http://www.jooq.org/download/

Cheers,
Aurélien

[Justin L]

Yes, I still use it myself.

But according to the avaje website there hasnt been a relase in 12 months where in 2013 (when I started using it) there were 4 releases that year.

I might just go with it anyway. I'm trying to do the Play + Spring Data tutorial but the template app doesnt even build. That's a bad sign in my opinion.

[Ian Rae]

A release of EBean occurred on Feb 9, according to the ebean newsgroup:

https://groups.google.com/forum/#!topic/ebean/Fl9IU7QW83k

However, Play 2.3 uses EBean 3.x, and the new ebean releases are 4.x, which require Play 2.4.

[Alex Loskutov]

I prefer Squeryl

It is very helpful lib which contains very simple SQL DSL 

http://squeryl.org/getting-started.html

понедельник, 23 марта 2015 г., 22:40:34 UTC+3 пользователь Justin L написал:

[Herman Banken]

I'm in favor of Squeryl as well. The fact that you have type-safety and still have the possibility to write extremely complex queries is just fantastic. 

It gives so much more confidence when changing your database model. When you apply an evolution, you at the same time need to make sure that your application models reflect the new Schema, which you'll do anyway if you need to access new fields. Then, during compilation, the Squeryl DSL will complain about renamed or removed fields as they no longer exist on your models.

Also you can just write your model once (case class Foo(field: String, whatever: Long)) and then Squeryl parses the rows, even complex ones which are the results of joins and aggregation queries/computes.

Squeryl can also generate SQL schema's. So if you want to go to full type-safety Squeryl could also be extended to act as an alternative to the Evolution plugin. Or it can complement it: checking if the schema in the database is different from the one it would generate itself. Then you could show a warning on startup. These things do not yet exist on top of Squeryl, but it would be quite easy to create.

[Onezino Gabriel Moreira]

Yeaph.

The ebean release that play 2.3 use is very out of date. I need to  try another solution because some bugs I has found.

My new fresh project now is using spring-data and I'm very confident about this.

[Eax Melanhovich]

I personally prefer Slick.

--
Best regards,
Eax Melanhovich
http://eax.me/

[Manuel Bernhardt]

Perhaps a bit outdated, but this gives an overview of existing options in Scala-Land: http://manuel.bernhardt.io/2014/02/04/a-quick-tour-of-relational-database-access-with-scala/

I investigated this for the purpose of integration with Play, so it should be relevant to your question

HTH

Manuel