Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion [2.0-scala] recommended ORM?

Received: by 10.42.32.8 with SMTP id b8mr343479icd.12.1349957015426;
        Thu, 11 Oct 2012 05:03:35 -0700 (PDT)
X-BeenThere: play-framework@googlegroups.com
Received: by 10.50.208.37 with SMTP id mb5ls3313523igc.2.gmail; Thu, 11 Oct
 2012 05:03:28 -0700 (PDT)
Received: by 10.50.182.132 with SMTP id ee4mr401420igc.5.1349957008396;
        Thu, 11 Oct 2012 05:03:28 -0700 (PDT)
Received: by 10.50.0.146 with SMTP id 18msige;
        Wed, 10 Oct 2012 21:40:22 -0700 (PDT)
Received: by 10.68.223.229 with SMTP id qx5mr3726pbc.15.1349930422727;
        Wed, 10 Oct 2012 21:40:22 -0700 (PDT)
Date: Wed, 10 Oct 2012 21:40:22 -0700 (PDT)
From: Sarvesh Kumar Singh <sarveshs...@gmail.com>
To: play-framework@googlegroups.com
Message-Id: <8000ec0f-139c-41ba-8a32-c740aeb0b270@googlegroups.com>
In-Reply-To: <CAP1F=qekTHRu5nkYG5y5DTJxSGDVSguEVeE+wdiDzzd5pii63w@mail.gmail.com>
References: <0896df91-09db-4e63-aaff-460d523a4399@googlegroups.com>
 <9532cb3a-e198-4197-8972-ce4a8a9ddff2@googlegroups.com>
 <CAF7j2av-5J5Pn=hvcy_12wPoNFJZHMw=ZRE5MeiyvAuDVEhisg@mail.gmail.com>
 <CAP1F=qekTHRu5nkYG5y5DTJxSGDVSguEVeE+wdiDzzd5pii63w@mail.gmail.com>
Subject: Re: [play-framework] Re: [2.0-scala] recommended ORM?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_297_15700282.1349930422105"

------=_Part_297_15700282.1349930422105
Content-Type: multipart/alternative; 
	boundary="----=_Part_298_2599579.1349930422105"

------=_Part_298_2599579.1349930422105
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I agree that the use of both of them will be straight forward.. but I think=
=20
that we
can safely assume that there will be various ( I mean way more than right=
=20
now )
community available modules for play in near future.

Now most of them will be using the default database approach ( if may be=20
Anorm
or Slick depending on how the devs goes), now in this case the point of=20
knowing
the "future of play" in terms of default database approach becomes=20
important.

More-ever there is already almost zero documentation for Anorm and if Play=
=20
drops it in future=20
then Anorm is sure to reach absolute zero and anyone having their important=
=20
apps written in using
Anorm will have to switch.

Considering these points I think that this is a pretty important question (=
=20
specially for start-ups with
few programmers).

Regards,
Sarvesh

On Wednesday, 10 October 2012 13:34:11 UTC+5:30, Julien Richard-Foy wrote:
>
> > I have some doubt about the persistence layer: Anorm or Slick?=20
>
> I think you should try both and pick the one which with you=E2=80=99re th=
e=20
> more comfortable. Slick and Anorm are very similar in a sense that=20
> both aren=E2=80=99t ORM.=20
>
> > Will Slick be the future standard for Play?=20
>
> I=E2=80=99m not sure to understand well your question: whatever you choos=
e,=20
> Anorm or Slick, their integration with Play is very straightforward,=20
> right?=20
>

------=_Part_298_2599579.1349930422105
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I agree that the use of both of them will be straight forward.. but I think=
 that we<br>can safely assume that there will be various ( I mean way more =
than right now )<br>community available modules for play in near future.<br=
><br>Now most of them will be using the default database approach ( if may =
be Anorm<br>or Slick depending on how the devs goes), now in this case the =
point of knowing<br>the "future of play" in terms of default database appro=
ach becomes important.<br><br>More-ever there is already almost zero docume=
ntation for Anorm and if Play drops it in future <br>then Anorm is sure to =
reach absolute zero and anyone having their important apps written in using=
<br>Anorm will have to switch.<br><br>Considering these points I think that=
 this is a pretty important question ( specially for start-ups with<br>few =
programmers).<br><br>Regards,<br>Sarvesh<br><br>On Wednesday, 10 October 20=
12 13:34:11 UTC+5:30, Julien Richard-Foy  wrote:<blockquote class=3D"gmail_=
quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;pa=
dding-left: 1ex;">&gt; I have some doubt about the persistence layer: Anorm=
 or Slick?
<br>
<br>I think you should try both and pick the one which with you=E2=80=99re =
the
<br>more comfortable. Slick and Anorm are very similar in a sense that
<br>both aren=E2=80=99t ORM.
<br>
<br>&gt; Will Slick be the future standard for Play?
<br>
<br>I=E2=80=99m not sure to understand well your question: whatever you cho=
ose,
<br>Anorm or Slick, their integration with Play is very straightforward,
<br>right?
<br></blockquote>
------=_Part_298_2599579.1349930422105--

------=_Part_297_15700282.1349930422105--