It seems that all the sample applications provided by the Play! framework make use of anorm for persistence. What is the reason for choosing anorm over an ORM? If you are using an ORM, what are you using and why?
相关问题
- Unusual use of the new keyword
- Get Runtime Type picked by implicit evidence
- What's the point of nonfinal singleton objects
- PlayFramework: how to transform each element of a
- Error in Scala Compiler: java.lang.AssertionError:
相关文章
- 用哪个ORM好点,博客园用的什么
- Gatling拓展插件开发,check(bodyString.saveAs("key"))怎么实现
- RDF libraries for Scala [closed]
- Why is my Dispatching on Actors scaled down in Akk
- Hibernate doesn't generate cascade
- How do you run cucumber with Scala 2.11 and sbt 0.
- GRPC: make high-throughput client in Java/Scala
- Is this the right way of using ThenFetch() to load
I think most of the arguments for anorm are listed on the corresponding page in the documentation.
For the time being I personally prefer a Scala and Play independent data access layer, thus I am using Ebean (and would be using JPA, if it was the recommended default).
Being able to use the Models without any Play-dependencies is a huge plus, in my opinion. Also Anorm does not seem to offer much database independence, since the queries are expressed in native SQL.
anorm is a meta acronym for Anorm is Not an Object Relational Mapper, hence it is not an ORM.
And therein lies the answer--it's for those of us who want to be hands-on with their SQL queries.