I noticed this too, a while back, and wondered about it. I believe the reason is that for folks who want to dump a database in order to start using DBIx::Class’s deployment tools, the authoritative view definition needs to start living in the .pm file. For folks, like myself, who manage the database itself and use dbicdump just to sync the .pm files with it, the view’s underlying query is useless in the .pm. I agree an option would be nice.
Thomas > On Jul 21, 2017, at 10:44 , Francisco Obispo <franci...@obispo.link> wrote: > > I created an RT ticket (I don’t know if it’s the right place), to document > this behavior which I believe is a bug: > > https://rt.cpan.org/Public/Bug/Display.html?id=122544 > <https://rt.cpan.org/Public/Bug/Display.html?id=122544> > The result is that .pm’s derived from a view from dbicdump are larger than > they need to be, inherently using more memory, and with no real good purpose. > There should be an option to turn this behavior off. > > regards > > _______________________________________________ > 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
_______________________________________________ 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
