DBIx::Class is not built for speed, it's built for convenience and
ease of use, but sometimes you just need to get the data, and skip the
-fancy objects. Luckily this is also fairly easy using
-C<inflate_result>:
-
- # Define a class which just returns the results as a hashref:
- package My::HashRefInflator;
-
- ## $me is the hashref of cols/data from the immediate resultsource
- ## $prefetch is a deep hashref of all the data from the prefetched
- ## related sources.
-
- sub mk_hash {
- my ($me, $rest) = @_;
-
- return { %$me,
- map { ($_ => mk_hash(@{$rest->{$_}})) } keys %$rest
- };
- }
-
- sub inflate_result {
- my ($self, $source, $me, $prefetch) = @_;
- return mk_hash($me, $prefetch);
- }
-
- # Change the object inflation to a hashref for just this resultset:
- $rs->result_class('My::HashRefInflator');
-
- my $datahashref = $rs->next;
- foreach my $col (keys %$datahashref) {
- if(!ref($datahashref->{$col})) {
- # It's a plain value
- }
- elsif(ref($datahashref->{$col} eq 'HASH')) {
- # It's a related value in a hashref
- }
- }
-
+fancy objects.
+
+To do this simply use L<DBIx::Class::ResultClass::HashRefInflator>.
+
+ my $rs = $schema->resultset('CD');
+
+ $rs->result_class('DBIx::Class::ResultClass::HashRefInflator');
+
+ my $hash_ref = $rs->find(1);
+
+Wasn't that easy?
+
=head2 Want to know if find_or_create found or created a row?
Just use C<find_or_new> instead, then check C<in_storage>:
package DBIx::Class::ResultClass::HashRefInflator;
-# $me is the hashref of cols/data from the immediate resultsource
-# $rest is a deep hashref of all the data from the prefetched
-# related sources.
+=head1 NAME
+
+DBIx::Class::ResultClass::HashRefInflator
+
+=head1 SYNOPSIS
+
+ my $rs = $schema->resultset('CD');
+
+ $rs->result_class('DBIx::Class::ResultClass::HashRefInflator');
+
+=head1 DESCRIPTION
+
+DBIx::Class is not built for speed: it's built for convenience and
+ease of use. But sometimes you just need to get the data, and skip the
+fancy objects. That is what this class provides.
+
+There are two ways of using this class.
+
+=over
+
+=item *
+
+Specify C<< $rs->result_class >> on a specific resultset to affect only that
+resultser (and any chained off of it); or
+
+=item *
+
+Specify C<< __PACKAGE__->result_class >> on your source object to force all
+uses of that result source to be inflated to hash-refs - this approach is not
+recomended
+
+=back
+
+=head1 METHODS
+
+=head2 inflate_result
+
+Inflates the result and prefetched data into a hash-ref using L<mk_hash>.
+
+=cut
+
+sub inflate_result {
+ my ($self, $source, $me, $prefetch) = @_;
+
+ return mk_hash($me, $prefetch);
+}
+
+=head2 mk_hash
+
+This does all the work of inflating the (pre)fetched data.
+
+=cut
sub mk_hash {
my ($me, $rest) = @_;
+ # $me is the hashref of cols/data from the immediate resultsource
+ # $rest is a deep hashref of all the data from the prefetched
+ # related sources.
+
# to avoid emtpy has_many rels contain one empty hashref
return if (not keys %$me);
return { %$me,
- map { ($_ => ref($rest->{$_}[0]) eq 'ARRAY' ? [ map { mk_hash(@$_) } @{$rest->{$_}} ] : mk_hash(@{$rest->{$_}}) ) } keys %$rest
+ map {
+ ( $_ =>
+ ref($rest->{$_}[0]) eq 'ARRAY' ? [ map { mk_hash(@$_) } @{$rest->{$_}} ]
+ : mk_hash( @{$rest->{$_}} )
+ )
+ } keys %$rest
};
}
-sub inflate_result {
- my ($self, $source, $me, $prefetch) = @_;
-
- return mk_hash($me, $prefetch);
-}
-
1;