My favorite often-overlooked method of avoiding having to set resultset_class on all your resultsets is to use load_namespaces instead of load_classes in your DBIx::Class::Schema subclass. For example, I usually set my schema up like this:

# lib/MyDB.pm
package MyDB;
use strict;
use warnings;
use base qw( DBIx::Class::Schema );

__PACKAGE__->load_namespaces(
    default_resultset_class => 'ResultSet',
);

1;

# lib/MyDB/ResultSet.pm
package MyDB::ResultSet;
use strict;
use warnings;
use base qw( DBIx::Class::ResultSet );

1;

# lib/MyDB/Result.pm
package MyDB::Result;
use strict;
use warnings;
use base qw( DBIx::Class );

__PACKAGE__->load_components(qw(
    FormFu
    InflateColumn::DateTime
    UUIDColumns
    Core
));

1;
[download]

This way I have a custom base class for both resultsets and results, and if I create a new result class or a new resultset class, it will just work, without having to do anything extra.

This also lets you add common functionality to your base classes, like I did with loading components I use everywhere in MyDB::Result. If you add custom functionality to your base MyDB::ResultSet class, that will get used whenever you don't have a specific resultset class for a given result class, which is handy for adding things like advanced searching to all your resultsets.

# lib/MyDB/Result/Article.pm
package MyDB::Result::Article;
use strict;
use warnings;
use base qw( MyDB::Result );

__PACKAGE__->table( 'articles' );
__PACKAGE__->columns(qw( updated_time created_time ));
[download]

Now, if I do this:

my $schema = MyDB->connect( @connection_info );
my $article = $rs->schema( 'Article' )->new({});
[download]

I'll get back a MyDB::Result::Article object that automatically has it's resultset_class set to MyDB::ResultSet. If I later decide I have functionality to add to the resultset just for articles (as you did), I can just create the new class and it will be detected automatically at startup.

# lib/MyDB/ResultSet/Article.pm
package MyDB::ResultSet::Article;
use strict;
use warnings;
use base qw( MyDB::ResultSet );

sub insert_article {
  my ($self, $topic, $parent, $msgtext) = @_;

  eval { $self->txn_do( sub {} ) };
}

1;
[download]

And now when doing my $article = $rs->schema( 'Article' )->new({});, the object I get back has it's resultset_class set to MyDB::ResultSet::Article instead, since there is a specific class for it now...