12 my $schema = DBICTest->init_schema();
13 my $sdebug = $schema->storage->debug;
16 # once the following TODO is complete, remove the 2 warning tests immediately
17 # after the TODO block
18 # (the TODO block itself contains tests ensuring that the warns are removed)
20 local $TODO = 'Prefetch of multiple has_many rels at the same level (currently warn to protect the clueless git)';
23 my $cd_rs = $schema->resultset('CD')->search ({ 'me.title' => 'Forkful of bees' });
24 my $pr_cd_rs = $cd_rs->search ({}, {
25 prefetch => [qw/tracks tags/],
28 my $tracks_rs = $cd_rs->first->tracks;
29 my $tracks_count = $tracks_rs->count;
31 my ($pr_tracks_rs, $pr_tracks_count);
34 $schema->storage->debugcb(sub { $queries++ });
35 $schema->storage->debug(1);
39 local $SIG{__WARN__} = sub { $o_mm_warn = shift };
40 $pr_tracks_rs = $pr_cd_rs->first->tracks;
42 $pr_tracks_count = $pr_tracks_rs->count;
44 ok(! $o_mm_warn, 'no warning on attempt to prefetch several same level has_many\'s (1 -> M + M)');
46 is($queries, 1, 'prefetch one->(has_many,has_many) ran exactly 1 query');
47 $schema->storage->debugcb (undef);
48 $schema->storage->debug ($sdebug);
50 is($pr_tracks_count, $tracks_count, 'equal count of prefetched relations over several same level has_many\'s (1 -> M + M)');
51 is ($pr_tracks_rs->all, $tracks_rs->all, 'equal amount of objects returned with and without prefetch over several same level has_many\'s (1 -> M + M)');
54 my $note_rs = $schema->resultset('LinerNotes')->search ({ notes => 'Buy Whiskey!' });
55 my $pr_note_rs = $note_rs->search ({}, {
57 cd => [qw/tracks tags/]
61 my $tags_rs = $note_rs->first->cd->tags;
62 my $tags_count = $tags_rs->count;
64 my ($pr_tags_rs, $pr_tags_count);
67 $schema->storage->debugcb(sub { $queries++ });
68 $schema->storage->debug(1);
72 local $SIG{__WARN__} = sub { $m_o_mm_warn = shift };
73 $pr_tags_rs = $pr_note_rs->first->cd->tags;
75 $pr_tags_count = $pr_tags_rs->count;
77 ok(! $m_o_mm_warn, 'no warning on attempt to prefetch several same level has_many\'s (M -> 1 -> M + M)');
79 is($queries, 1, 'prefetch one->(has_many,has_many) ran exactly 1 query');
80 $schema->storage->debugcb (undef);
81 $schema->storage->debug ($sdebug);
83 is($pr_tags_count, $tags_count, 'equal count of prefetched relations over several same level has_many\'s (M -> 1 -> M + M)');
84 is($pr_tags_rs->all, $tags_rs->all, 'equal amount of objects with and without prefetch over several same level has_many\'s (M -> 1 -> M + M)');
87 # remove this closure once the TODO above is working
89 my $warn_re = qr/will explode the number of row objects retrievable via/;
92 local $SIG{__WARN__} = sub { $_[0] =~ $warn_re ? push @w, @_ : warn @_ };
94 my $rs = $schema->resultset('CD')->search ({ 'me.title' => 'Forkful of bees' }, { prefetch => [qw/tracks tags/] });
97 is (@w, 1, 'warning on attempt prefetching several same level has_manys (1 -> M + M)');
99 my $rs2 = $schema->resultset('LinerNotes')->search ({ notes => 'Buy Whiskey!' }, { prefetch => { cd => [qw/tags tracks/] } });
101 @dummy = $rs2->first;
102 is (@w, 1, 'warning on attempt prefetching several same level has_manys (M -> 1 -> M + M)');
106 The solution is to rewrite ResultSet->_collapse_result() and
107 ResultSource->resolve_prefetch() to focus on the final results from the collapse
108 of the data. Right now, the code doesn't treat the columns from the various
109 tables as grouped entities. While there is a concept of hierarchy (so that
110 prefetching down relationships does work as expected), there is no idea of what
111 the final product should look like and how the various columns in the row would
112 play together. So, the actual prefetch datastructure from the search would be
113 very useful in working through this problem. We already have access to the PKs
114 and sundry for those. So, when collapsing the search result, we know we are
115 looking for 1 cd object. We also know we're looking for tracks and tags records
116 -independently- of each other. So, we can grab the data for tracks and data for
117 tags separately, uniqueing on the PK as appropriate. Then, when we're done with
118 the given cd object's datastream, we know we're good. This should work for all
119 the various scenarios.
121 My reccommendation is the row's data is preprocessed first, breaking it up into
122 the data for each of the component tables. (This could be done in the single
123 table case, too, but probably isn't necessary.) So, starting with something
133 it is massaged to look something like:
135 t1 => { col1 => 1, col2 => 2 },
136 t2 => { col1 => 3, col2 => 4 },
137 t3 => { col1 => 5, col2 => 6 },
139 At this point, find the stuff that's different is easy enough to do and slotting
140 things into the right spot is, likewise, pretty straightforward. Instead of
141 storing things in a AoH, store them in a HoH keyed on the PKs of the the table,
142 then convert to an AoH after all collapsing is done.
144 This implies that the collapse attribute can probably disappear or, at the
145 least, be turned into a boolean (which is how it's used in every other place).