On Fri, May 11, 2012 at 06:40:26PM +0100, Matt S Trout wrote:
> > I contacted the DBIx::ResultSet maintainer last year and sent
> > him a long e-mail with ideas and patches for new features. I got
> > no answer.
> > After a couple months, I tried again. Still no answer.
> > Then I tried again. An
On 11-05-2012 at 17:07, Matt S Trout wrote:
>What does this achieve that the already existing lightr-DBIx::Class
>module DBIx::ResultSet doesn't
Accessor methods, custom packages, relationships, joins,
group_by, ->next, ->single and more...
Also, DBIx::ResultSet is clearly not an ORM.
>an
On Fri, May 11, 2012 at 07:22:42PM +0200, Alessandro Ranellucci wrote:
> On 11-05-2012 at 17:07, Matt S Trout wrote:
>
> >What does this achieve that the already existing lightr-DBIx::Class
> >module DBIx::ResultSet doesn't
>
> Accessor methods, custom packages, relationships, joins,
> group_b
On Fri, May 11, 2012 at 02:10:26PM +0200, Perl Authors Upload Server wrote:
> The well-known DBIx::Class provides a powerful way to abstract
> database queries, but it requires full table definitions and a bunch
> of .pm files in order to define a schema.
Also, no it doesn't.
Kioku's
On Fri, May 11, 2012 at 02:10:26PM +0200, Perl Authors Upload Server wrote:
>
> The following module was proposed for inclusion in the Module List:
>
> modid: DBIx::Lite
> DSLIP: RdpOp
> description: Chained and minimal ORM
> userid: AAR (Alessandro Ranellucci)
> chapte
The following module was proposed for inclusion in the Module List:
modid: DBIx::Lite
DSLIP: RdpOp
description: Chained and minimal ORM
userid: AAR (Alessandro Ranellucci)
chapterid: 7 (Database_Interfaces)
communities:
IRC and GitHub repository (pull requests)
