Thanks for all the work on this guys. Things seem to be working well with one small issue and one big-ish one. The small one is that mixing load_components() and Moo's extends() doesn't work. Easy enough to fix and makes sense.
The larger issue is that now, with latest Moo, the method resolution order changes from 'c3' to 'dfs' which breaks a bunch of things for me. For example DBIx::Class::InflateColumn::DateTime, under c3, comes before DBIx::Class::Row, but with dfs it comes after and column inflation stops functioning. Doing this in my result classes seems to fix it: use Moo; use mro 'c3'; I should be complete with my DBIC->Moo work within the next day or two and I'm hoping based on early success that all will be well. Aran On Sat, Dec 20, 2014 at 6:29 AM Peter Rabbitson <rabbit+d...@rabbit.us> wrote: > On 10/02/2014 04:21 AM, Aran Deltac wrote: > > I've been converting a lot of @work's custom components, result, result > > set, schema, and storage classes (yes, we even have custom storage > > classes) to Moo roles and classes. > > > > Hi Aran, > > Just wanted to followup whether the current stable DBIC and Moo versions > resolve your issues. > > Thanks! > >
_______________________________________________ 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
