Peter, thanks!
Right now I use a wrapper around ResultSet->all and set_cache for childs.
And in code I retrieve all data at once via ->all.
On 2 May 2013 15:01, Peter Rabbitson <rabbit+d...@rabbit.us> wrote:
> On Thu, May 02, 2013 at 08:57:30PM +1000, Peter Rabbitson wrote:
> >
> > *) Allow {cursor} to be set (either via cursor() or make a separate
> setter)
> > *) Make it accept a coderef
> > *) Teach all()/next()/single() to pre-populate {_stashed_rows}
> > *) Make _construct_results() aware of this somehow (handwave)
> > *) Profit
> >
>
> In case this part is unclear - I am not saying the internals above
> (apart from the official API) are stable and will remain in the
> codebase. This is just a suggestion how to experiment *today* so a
> proper API supported by tests can be devised later.
>
> In other words if you just take my advice, implement something in house
> and never talk to us again - we *will* eventually break your code ;)
>
> Cheers
>
>
> _______________________________________________
> List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
> IRC: irc.perl.org#dbix-class
> SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
> Searchable Archive:
> http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
>
--
//wbr, Dmitry L.
_______________________________________________
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
