On Sat, Aug 23, 2008 at 09:44:19AM +0200, Matija Grabnar wrote:
> Alex Peters wrote:
> >Perhaps there's a (very well hidden) Moose plugin that makes
> >the whole process trivial?
> >
> You mean, something like this
> http://www.yapceurope2008.org/ye2008/talk/1345
http://code2.0beta.co.uk/reactio
On Sat, Aug 23, 2008 at 02:22:06PM +1000, Alex Peters wrote:
> Hi,
>
> I'm starting a new project using Moose[1] and am wondering how
> best to handle persistent storage of these Moose objects.
>
> If I weren't using Moose, DBIx::Class would be the obvious
> answer here. However, in a way Moose
On Sat, 23 Aug 2008, Alex Peters wrote:
Hi,
I'm starting a new project using Moose[1] and am wondering how
best to handle persistent storage of these Moose objects.
If I weren't using Moose, DBIx::Class would be the obvious
answer here. However, in a way Moose and DBIx::Class seem to
overla
> Alex Peters wrote:
> > Perhaps there's a (very well hidden) Moose plugin that makes
> > the whole process trivial?
>
> You mean, something like this
> http://www.yapceurope2008.org/ye2008/talk/1345
Apart from JRockway's presentation in Copenhagen there seem to exist no
documentation about Ernst
Alex Peters wrote:
Perhaps there's a (very well hidden) Moose plugin that makes
the whole process trivial?
You mean, something like this
http://www.yapceurope2008.org/ye2008/talk/1345
___
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/db
Hi,
I'm starting a new project using Moose[1] and am wondering how
best to handle persistent storage of these Moose objects.
If I weren't using Moose, DBIx::Class would be the obvious
answer here. However, in a way Moose and DBIx::Class seem to
overlap in terms of the functionality that they pro
