From: Konstantinos Kougios <kostas.koug...@googlemail.com>
Date: Fri, 02 Nov 2012 21:58:48 +0000
Local: Fri, Nov 2 2012 5:58 pm
Subject: Re: [scala-user] Re: Scala and databases
Thanks for the example Flavio, ok I see. Why the emphasis on mapperdao uses a different approach and your example would look like
class Stock(val code:String,val categories:Set[Category]) // or You can too use an intermediate StockCategory entity if you prefer.
MapperDao gives direct control on persistence and transactions to client val tx = Transaction.get(txManager, Propagation.Nested, }
MapperDao supports nested transactions too along with updates/deletes. All web frameworks are supported as mapperdao only needs a DataSource to work. A major feature of mapperdao is support for immutable classes, something that i.e. hibernate doesn't support, along with a typesafe DSL for querying. On 02/11/12 20:06, Flávio W. Brasil wrote:
> Hello.
> Activate is designed to be simple. OO is straightforward to map data > class Stock(var code: String) extends Entity {
> To map the same domain using separate entity declaration and > class Person(var name: String, var contacts: List[Contact]) extends Entity
> There are characteristics that makes Activate different from Slick, > -- > On Thursday, 1 de November de 2012 at 19:43, Konstantinos Kougios wrote:
>> I had a look at activate, I couldn't find a complete example with say >> On 01/11/12 12:52, Rafał Krzewski wrote:
>>> Well, there is at least one other: >>> Cheers,
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||