Commit | Line | Data |
55e2d745 |
1 | package DBIx::Class::Relationship::Base; |
2 | |
3 | use strict; |
4 | use warnings; |
5 | |
1edd1722 |
6 | use base qw/DBIx::Class/; |
6298a324 |
7 | |
8 | use Scalar::Util qw/weaken blessed/; |
ed7ab0f4 |
9 | use Try::Tiny; |
fd323bf1 |
10 | use namespace::clean; |
55e2d745 |
11 | |
75d07914 |
12 | =head1 NAME |
55e2d745 |
13 | |
8918977e |
14 | DBIx::Class::Relationship::Base - Inter-table relationships |
55e2d745 |
15 | |
16 | =head1 SYNOPSIS |
17 | |
6c4f4d69 |
18 | __PACKAGE__->add_relationship( |
19 | spiders => 'My::DB::Result::Creatures', |
20 | sub { |
21 | my $args = shift; |
22 | return { |
23 | "$args->{foreign_alias}.id" => { -ident => "$args->{self_alias}.id" }, |
24 | "$args->{foreign_alias}.type" => 'arachnid' |
25 | }; |
26 | }, |
27 | ); |
13523f29 |
28 | |
55e2d745 |
29 | =head1 DESCRIPTION |
30 | |
30236e47 |
31 | This class provides methods to describe the relationships between the |
32 | tables in your database model. These are the "bare bones" relationships |
75d07914 |
33 | methods, for predefined ones, look in L<DBIx::Class::Relationship>. |
55e2d745 |
34 | |
35 | =head1 METHODS |
36 | |
8091aa91 |
37 | =head2 add_relationship |
503536d5 |
38 | |
27f01d1f |
39 | =over 4 |
40 | |
13523f29 |
41 | =item Arguments: 'relname', 'Foreign::Class', $condition, $attrs |
27f01d1f |
42 | |
43 | =back |
30236e47 |
44 | |
6c4f4d69 |
45 | __PACKAGE__->add_relationship('relname', |
46 | 'Foreign::Class', |
13523f29 |
47 | $condition, $attrs); |
48 | |
49 | Create a custom relationship between one result source and another |
50 | source, indicated by its class name. |
503536d5 |
51 | |
406734bb |
52 | =head3 condition |
53 | |
6c4f4d69 |
54 | The condition argument describes the C<ON> clause of the C<JOIN> |
55 | expression used to connect the two sources when creating SQL queries. |
30236e47 |
56 | |
13523f29 |
57 | To create simple equality joins, supply a hashref containing the |
58 | remote table column name as the key(s), and the local table column |
6c4f4d69 |
59 | name as the value(s), for example given: |
503536d5 |
60 | |
6c4f4d69 |
61 | My::Schema::Author->has_many( |
62 | books => 'My::Schema::Book', |
63 | { 'foreign.author_id' => 'self.id' } |
64 | ); |
503536d5 |
65 | |
6c4f4d69 |
66 | A query like: |
67 | |
68 | $author_rs->search_related('books')->next |
503536d5 |
69 | |
6c4f4d69 |
70 | will result in the following C<JOIN> clause: |
71 | |
72 | ... FROM author me LEFT JOIN book books ON books.author_id = me.id ... |
503536d5 |
73 | |
13523f29 |
74 | This describes a relationship between the C<Author> table and the |
75 | C<Book> table where the C<Book> table has a column C<author_id> |
76 | containing the ID value of the C<Author>. |
77 | |
6c4f4d69 |
78 | C<foreign> and C<self> are pseudo aliases and must be entered |
13523f29 |
79 | literally. They will be replaced with the actual correct table alias |
80 | when the SQL is produced. |
81 | |
82 | Similarly: |
5271499d |
83 | |
6c4f4d69 |
84 | My::Schema::Book->has_many( |
85 | editions => 'My::Schema::Edition', |
86 | { |
87 | 'foreign.publisher_id' => 'self.publisher_id', |
88 | 'foreign.type_id' => 'self.type_id', |
89 | } |
90 | ); |
91 | |
92 | ... |
93 | |
94 | $book_rs->search_related('editions')->next |
5271499d |
95 | |
13523f29 |
96 | will result in the C<JOIN> clause: |
5271499d |
97 | |
6c4f4d69 |
98 | ... FROM book me |
99 | LEFT JOIN edition editions ON |
100 | editions.publisher_id = me.publisher_id |
101 | AND editions.type_id = me.type_id ... |
5271499d |
102 | |
13523f29 |
103 | This describes the relationship from C<Book> to C<Edition>, where the |
104 | C<Edition> table refers to a publisher and a type (e.g. "paperback"): |
105 | |
106 | As is the default in L<SQL::Abstract>, the key-value pairs will be |
107 | C<AND>ed in the result. C<OR> can be achieved with an arrayref, for |
6c4f4d69 |
108 | example a condition like: |
13523f29 |
109 | |
6c4f4d69 |
110 | My::Schema::Item->has_many( |
111 | related_item_links => My::Schema::Item::Links, |
112 | [ |
113 | { 'foreign.left_itemid' => 'self.id' }, |
114 | { 'foreign.right_itemid' => 'self.id' }, |
115 | ], |
116 | ); |
13523f29 |
117 | |
6c4f4d69 |
118 | will translate to the following C<JOIN> clause: |
13523f29 |
119 | |
6c4f4d69 |
120 | ... FROM item me JOIN item_relations related_item_links ON |
121 | related_item_links.left_itemid = me.id |
122 | OR related_item_links.right_itemid = me.id ... |
13523f29 |
123 | |
6c4f4d69 |
124 | This describes the relationship from C<Item> to C<Item::Links>, where |
125 | C<Item::Links> is a many-to-many linking table, linking items back to |
126 | themselves in a peer fashion (without a "parent-child" designation) |
13523f29 |
127 | |
6c4f4d69 |
128 | To specify joins which describe more than a simple equality of column |
129 | values, the custom join condition coderef syntax can be used. For |
130 | example: |
13523f29 |
131 | |
6c4f4d69 |
132 | My::Schema::Artist->has_many( |
133 | cds_80s => 'My::Schema::CD', |
13523f29 |
134 | sub { |
6c4f4d69 |
135 | my $args = shift; |
13523f29 |
136 | |
6c4f4d69 |
137 | return { |
138 | "$args->{foreign_alias}.artist" => { -ident => "$args->{self_alias}.artistid" }, |
139 | "$args->{foreign_alias}.year" => { '>', "1979", '<', "1990" }, |
140 | }; |
141 | } |
142 | ); |
13523f29 |
143 | |
6c4f4d69 |
144 | ... |
13523f29 |
145 | |
6c4f4d69 |
146 | $artist_rs->search_related('cds_80s')->next; |
13523f29 |
147 | |
6c4f4d69 |
148 | will result in the C<JOIN> clause: |
13523f29 |
149 | |
6c4f4d69 |
150 | ... FROM artist me LEFT JOIN cd cds_80s ON |
151 | cds_80s.artist = me.artistid |
152 | AND cds_80s.year < ? |
153 | AND cds_80s.year > ? |
13523f29 |
154 | |
6c4f4d69 |
155 | with the bind values: |
13523f29 |
156 | |
6c4f4d69 |
157 | '1990', '1979' |
13523f29 |
158 | |
6c4f4d69 |
159 | C<< $args->{foreign_alias} >> and C<< $args->{self_alias} >> are supplied the |
160 | same values that would be otherwise substituted for C<foreign> and C<self> |
161 | in the simple hashref syntax case. |
162 | |
163 | The coderef is expected to return a valid L<SQL::Abstract> query-structure, just |
164 | like what one would supply as the first argument to |
165 | L<DBIx::Class::ResultSet/search>. The return value will be passed directly to |
166 | L<SQL::Abstract> and the resulting SQL will be used verbatim as the C<ON> |
167 | clause of the C<JOIN> statement associated with this relationship. |
168 | |
169 | While every coderef-based condition must return a valid C<ON> clause, it may |
8273e845 |
170 | elect to additionally return a simplified join-free condition hashref when |
6c4f4d69 |
171 | invoked as C<< $row_object->relationship >>, as opposed to |
172 | C<< $rs->related_resultset('relationship') >>. In this case C<$row_object> is |
173 | passed to the coderef as C<< $args->{self_rowobj} >>, so a user can do the |
174 | following: |
175 | |
176 | sub { |
177 | my $args = shift; |
178 | |
179 | return ( |
180 | { |
181 | "$args->{foreign_alias}.artist" => { -ident => "$args->{self_alias}.artistid" }, |
182 | "$args->{foreign_alias}.year" => { '>', "1979", '<', "1990" }, |
183 | }, |
184 | $args->{self_rowobj} && { |
185 | "$args->{foreign_alias}.artist" => $args->{self_rowobj}->artistid, |
186 | "$args->{foreign_alias}.year" => { '>', "1979", '<', "1990" }, |
187 | }, |
188 | ); |
13523f29 |
189 | } |
190 | |
191 | Now this code: |
192 | |
193 | my $artist = $schema->resultset("Artist")->find({ id => 4 }); |
194 | $artist->cds_80s->all; |
195 | |
6c4f4d69 |
196 | Can skip a C<JOIN> altogether and instead produce: |
13523f29 |
197 | |
6c4f4d69 |
198 | SELECT cds_80s.cdid, cds_80s.artist, cds_80s.title, cds_80s.year, cds_80s.genreid, cds_80s.single_track |
199 | FROM cd cds_80s |
200 | WHERE cds_80s.artist = ? |
201 | AND cds_80s.year < ? |
202 | AND cds_80s.year > ? |
13523f29 |
203 | |
204 | With the bind values: |
205 | |
206 | '4', '1990', '1979' |
207 | |
6c4f4d69 |
208 | Note that in order to be able to use |
209 | L<< $row->create_related|DBIx::Class::Relationship::Base/create_related >>, |
210 | the coderef must not only return as its second such a "simple" condition |
211 | hashref which does not depend on joins being available, but the hashref must |
212 | contain only plain values/deflatable objects, such that the result can be |
213 | passed directly to L<DBIx::Class::Relationship::Base/set_from_related>. For |
214 | instance the C<year> constraint in the above example prevents the relationship |
215 | from being used to to create related objects (an exception will be thrown). |
216 | |
217 | In order to allow the user to go truly crazy when generating a custom C<ON> |
218 | clause, the C<$args> hashref passed to the subroutine contains some extra |
219 | metadata. Currently the supplied coderef is executed as: |
220 | |
221 | $relationship_info->{cond}->({ |
222 | self_alias => The alias of the invoking resultset ('me' in case of a row object), |
223 | foreign_alias => The alias of the to-be-joined resultset (often matches relname), |
224 | self_resultsource => The invocant's resultsource, |
225 | foreign_relname => The relationship name (does *not* always match foreign_alias), |
226 | self_rowobj => The invocant itself in case of $row_obj->relationship |
227 | }); |
8091aa91 |
228 | |
406734bb |
229 | =head3 attributes |
230 | |
231 | The L<standard ResultSet attributes|DBIx::Class::ResultSet/ATTRIBUTES> may |
232 | be used as relationship attributes. In particular, the 'where' attribute is |
233 | useful for filtering relationships: |
234 | |
235 | __PACKAGE__->has_many( 'valid_users', 'MyApp::Schema::User', |
236 | { 'foreign.user_id' => 'self.user_id' }, |
237 | { where => { valid => 1 } } |
238 | ); |
239 | |
240 | The following attributes are also valid: |
8091aa91 |
241 | |
242 | =over 4 |
243 | |
244 | =item join_type |
245 | |
246 | Explicitly specifies the type of join to use in the relationship. Any SQL |
247 | join type is valid, e.g. C<LEFT> or C<RIGHT>. It will be placed in the SQL |
248 | command immediately before C<JOIN>. |
249 | |
97c96475 |
250 | =item proxy =E<gt> $column | \@columns | \%column |
251 | |
9ab122aa |
252 | The 'proxy' attribute can be used to retrieve values, and to perform |
253 | updates if the relationship has 'cascade_update' set. The 'might_have' |
254 | and 'has_one' relationships have this set by default; if you want a proxy |
255 | to update across a 'belongs_to' relationship, you must set the attribute |
256 | yourself. |
257 | |
97c96475 |
258 | =over 4 |
259 | |
260 | =item \@columns |
8091aa91 |
261 | |
30236e47 |
262 | An arrayref containing a list of accessors in the foreign class to create in |
8091aa91 |
263 | the main class. If, for example, you do the following: |
d4daee7b |
264 | |
03460bef |
265 | MyApp::Schema::CD->might_have(liner_notes => 'MyApp::Schema::LinerNotes', |
27f01d1f |
266 | undef, { |
267 | proxy => [ qw/notes/ ], |
268 | }); |
d4daee7b |
269 | |
03460bef |
270 | Then, assuming MyApp::Schema::LinerNotes has an accessor named notes, you can do: |
8091aa91 |
271 | |
03460bef |
272 | my $cd = MyApp::Schema::CD->find(1); |
30236e47 |
273 | $cd->notes('Notes go here'); # set notes -- LinerNotes object is |
274 | # created if it doesn't exist |
d4daee7b |
275 | |
9ab122aa |
276 | For a 'belongs_to relationship, note the 'cascade_update': |
277 | |
278 | MyApp::Schema::Track->belongs_to( cd => 'DBICTest::Schema::CD', 'cd, |
279 | { proxy => ['title'], cascade_update => 1 } |
280 | ); |
281 | $track->title('New Title'); |
282 | $track->update; # updates title in CD |
283 | |
97c96475 |
284 | =item \%column |
285 | |
286 | A hashref where each key is the accessor you want installed in the main class, |
287 | and its value is the name of the original in the fireign class. |
288 | |
03460bef |
289 | MyApp::Schema::Track->belongs_to( cd => 'DBICTest::Schema::CD', 'cd', { |
97c96475 |
290 | proxy => { cd_title => 'title' }, |
291 | }); |
292 | |
293 | This will create an accessor named C<cd_title> on the C<$track> row object. |
294 | |
295 | =back |
296 | |
297 | NOTE: you can pass a nested struct too, for example: |
298 | |
03460bef |
299 | MyApp::Schema::Track->belongs_to( cd => 'DBICTest::Schema::CD', 'cd', { |
97c96475 |
300 | proxy => [ 'year', { cd_title => 'title' } ], |
301 | }); |
302 | |
8091aa91 |
303 | =item accessor |
304 | |
305 | Specifies the type of accessor that should be created for the relationship. |
306 | Valid values are C<single> (for when there is only a single related object), |
307 | C<multi> (when there can be many), and C<filter> (for when there is a single |
308 | related object, but you also want the relationship accessor to double as |
309 | a column accessor). For C<multi> accessors, an add_to_* method is also |
310 | created, which calls C<create_related> for the relationship. |
311 | |
3d618782 |
312 | =item is_foreign_key_constraint |
313 | |
314 | If you are using L<SQL::Translator> to create SQL for you and you find that it |
fd323bf1 |
315 | is creating constraints where it shouldn't, or not creating them where it |
3d618782 |
316 | should, set this attribute to a true or false value to override the detection |
317 | of when to create constraints. |
318 | |
5f7ac523 |
319 | =item cascade_copy |
320 | |
321 | If C<cascade_copy> is true on a C<has_many> relationship for an |
322 | object, then when you copy the object all the related objects will |
fd323bf1 |
323 | be copied too. To turn this behaviour off, pass C<< cascade_copy => 0 >> |
324 | in the C<$attr> hashref. |
b7bbc39f |
325 | |
326 | The behaviour defaults to C<< cascade_copy => 1 >> for C<has_many> |
327 | relationships. |
5f7ac523 |
328 | |
329 | =item cascade_delete |
330 | |
b7bbc39f |
331 | By default, DBIx::Class cascades deletes across C<has_many>, |
332 | C<has_one> and C<might_have> relationships. You can disable this |
fd323bf1 |
333 | behaviour on a per-relationship basis by supplying |
b7bbc39f |
334 | C<< cascade_delete => 0 >> in the relationship attributes. |
5f7ac523 |
335 | |
336 | The cascaded operations are performed after the requested delete, |
337 | so if your database has a constraint on the relationship, it will |
338 | have deleted/updated the related records or raised an exception |
339 | before DBIx::Class gets to perform the cascaded operation. |
340 | |
341 | =item cascade_update |
342 | |
b7bbc39f |
343 | By default, DBIx::Class cascades updates across C<has_one> and |
5f7ac523 |
344 | C<might_have> relationships. You can disable this behaviour on a |
b7bbc39f |
345 | per-relationship basis by supplying C<< cascade_update => 0 >> in |
346 | the relationship attributes. |
5f7ac523 |
347 | |
9ab122aa |
348 | The C<belongs_to> relationship does not update across relationships |
349 | by default, so if you have a 'proxy' attribute on a belongs_to and want to |
350 | use 'update' on it, you muse set C<< cascade_update => 1 >>. |
351 | |
cee0c9b1 |
352 | This is not a RDMS style cascade update - it purely means that when |
353 | an object has update called on it, all the related objects also |
354 | have update called. It will not change foreign keys automatically - |
355 | you must arrange to do this yourself. |
5f7ac523 |
356 | |
e377d723 |
357 | =item on_delete / on_update |
358 | |
359 | If you are using L<SQL::Translator> to create SQL for you, you can use these |
fd323bf1 |
360 | attributes to explicitly set the desired C<ON DELETE> or C<ON UPDATE> constraint |
361 | type. If not supplied the SQLT parser will attempt to infer the constraint type by |
e377d723 |
362 | interrogating the attributes of the B<opposite> relationship. For any 'multi' |
fd323bf1 |
363 | relationship with C<< cascade_delete => 1 >>, the corresponding belongs_to |
364 | relationship will be created with an C<ON DELETE CASCADE> constraint. For any |
e377d723 |
365 | relationship bearing C<< cascade_copy => 1 >> the resulting belongs_to constraint |
366 | will be C<ON UPDATE CASCADE>. If you wish to disable this autodetection, and just |
fd323bf1 |
367 | use the RDBMS' default constraint type, pass C<< on_delete => undef >> or |
e377d723 |
368 | C<< on_delete => '' >>, and the same for C<on_update> respectively. |
369 | |
13de943d |
370 | =item is_deferrable |
371 | |
372 | Tells L<SQL::Translator> that the foreign key constraint it creates should be |
373 | deferrable. In other words, the user may request that the constraint be ignored |
374 | until the end of the transaction. Currently, only the PostgreSQL producer |
375 | actually supports this. |
376 | |
2581038c |
377 | =item add_fk_index |
378 | |
379 | Tells L<SQL::Translator> to add an index for this constraint. Can also be |
380 | specified globally in the args to L<DBIx::Class::Schema/deploy> or |
381 | L<DBIx::Class::Schema/create_ddl_dir>. Default is on, set to 0 to disable. |
382 | |
8091aa91 |
383 | =back |
384 | |
87c4e602 |
385 | =head2 register_relationship |
386 | |
27f01d1f |
387 | =over 4 |
388 | |
ebc77b53 |
389 | =item Arguments: $relname, $rel_info |
27f01d1f |
390 | |
391 | =back |
71e65b39 |
392 | |
30236e47 |
393 | Registers a relationship on the class. This is called internally by |
71f9df37 |
394 | DBIx::Class::ResultSourceProxy to set up Accessors and Proxies. |
71e65b39 |
395 | |
55e2d745 |
396 | =cut |
397 | |
71e65b39 |
398 | sub register_relationship { } |
399 | |
27f01d1f |
400 | =head2 related_resultset |
401 | |
402 | =over 4 |
403 | |
ebc77b53 |
404 | =item Arguments: $relationship_name |
27f01d1f |
405 | |
d601dc88 |
406 | =item Return Value: $related_resultset |
27f01d1f |
407 | |
408 | =back |
30236e47 |
409 | |
27f01d1f |
410 | $rs = $cd->related_resultset('artist'); |
30236e47 |
411 | |
27f01d1f |
412 | Returns a L<DBIx::Class::ResultSet> for the relationship named |
413 | $relationship_name. |
30236e47 |
414 | |
415 | =cut |
416 | |
417 | sub related_resultset { |
418 | my $self = shift; |
bc0c9800 |
419 | $self->throw_exception("Can't call *_related as class methods") |
420 | unless ref $self; |
30236e47 |
421 | my $rel = shift; |
164efde3 |
422 | my $rel_info = $self->relationship_info($rel); |
bc0c9800 |
423 | $self->throw_exception( "No such relationship ${rel}" ) |
164efde3 |
424 | unless $rel_info; |
d4daee7b |
425 | |
30236e47 |
426 | return $self->{related_resultsets}{$rel} ||= do { |
427 | my $attrs = (@_ > 1 && ref $_[$#_] eq 'HASH' ? pop(@_) : {}); |
164efde3 |
428 | $attrs = { %{$rel_info->{attrs} || {}}, %$attrs }; |
30236e47 |
429 | |
bc0c9800 |
430 | $self->throw_exception( "Invalid query: @_" ) |
431 | if (@_ > 1 && (@_ % 2 == 1)); |
30236e47 |
432 | my $query = ((@_ > 1) ? {@_} : shift); |
433 | |
68f3b0dd |
434 | my $source = $self->result_source; |
d419ded6 |
435 | |
436 | # condition resolution may fail if an incomplete master-object prefetch |
34b6b86f |
437 | # is encountered - that is ok during prefetch construction (not yet in_storage) |
aa56106b |
438 | my ($cond, $is_crosstable) = try { |
16053767 |
439 | $source->_resolve_condition( $rel_info->{cond}, $rel, $self, $rel ) |
52b420dd |
440 | } |
ed7ab0f4 |
441 | catch { |
34b6b86f |
442 | if ($self->in_storage) { |
ed7ab0f4 |
443 | $self->throw_exception ($_); |
34b6b86f |
444 | } |
52b420dd |
445 | |
446 | $DBIx::Class::ResultSource::UNRESOLVABLE_CONDITION; # RV |
ed7ab0f4 |
447 | }; |
d419ded6 |
448 | |
aa56106b |
449 | # keep in mind that the following if() block is part of a do{} - no return()s!!! |
450 | if ($is_crosstable) { |
451 | $self->throw_exception ( |
452 | "A cross-table relationship condition returned for statically declared '$rel'") |
453 | unless ref $rel_info->{cond} eq 'CODE'; |
454 | |
455 | # A WHOREIFFIC hack to reinvoke the entire condition resolution |
456 | # with the correct alias. Another way of doing this involves a |
457 | # lot of state passing around, and the @_ positions are already |
458 | # mapped out, making this crap a less icky option. |
459 | # |
460 | # The point of this exercise is to retain the spirit of the original |
461 | # $obj->search_related($rel) where the resulting rset will have the |
462 | # root alias as 'me', instead of $rel (as opposed to invoking |
463 | # $rs->search_related) |
464 | |
aa56106b |
465 | local $source->{_relationships}{me} = $source->{_relationships}{$rel}; # make the fake 'me' rel |
466 | my $obj_table_alias = lc($source->source_name) . '__row'; |
93508f48 |
467 | $obj_table_alias =~ s/\W+/_/g; |
aa56106b |
468 | |
469 | $source->resultset->search( |
470 | $self->ident_condition($obj_table_alias), |
471 | { alias => $obj_table_alias }, |
472 | )->search_related('me', $query, $attrs) |
68f3b0dd |
473 | } |
aa56106b |
474 | else { |
475 | # FIXME - this conditional doesn't seem correct - got to figure out |
476 | # at some point what it does. Also the entire UNRESOLVABLE_CONDITION |
477 | # business seems shady - we could simply not query *at all* |
478 | if ($cond eq $DBIx::Class::ResultSource::UNRESOLVABLE_CONDITION) { |
479 | my $reverse = $source->reverse_relationship_info($rel); |
480 | foreach my $rev_rel (keys %$reverse) { |
481 | if ($reverse->{$rev_rel}{attrs}{accessor} && $reverse->{$rev_rel}{attrs}{accessor} eq 'multi') { |
0a03206a |
482 | weaken($attrs->{related_objects}{$rev_rel}[0] = $self); |
aa56106b |
483 | } else { |
0a03206a |
484 | weaken($attrs->{related_objects}{$rev_rel} = $self); |
aa56106b |
485 | } |
486 | } |
9aae3566 |
487 | } |
aa56106b |
488 | elsif (ref $cond eq 'ARRAY') { |
7689b9e5 |
489 | $cond = [ map { |
490 | if (ref $_ eq 'HASH') { |
491 | my $hash; |
492 | foreach my $key (keys %$_) { |
493 | my $newkey = $key !~ /\./ ? "me.$key" : $key; |
494 | $hash->{$newkey} = $_->{$key}; |
495 | } |
496 | $hash; |
497 | } else { |
498 | $_; |
370f2ba2 |
499 | } |
7689b9e5 |
500 | } @$cond ]; |
aa56106b |
501 | } |
502 | elsif (ref $cond eq 'HASH') { |
503 | foreach my $key (grep { ! /\./ } keys %$cond) { |
7689b9e5 |
504 | $cond->{"me.$key"} = delete $cond->{$key}; |
370f2ba2 |
505 | } |
30236e47 |
506 | } |
a126983e |
507 | |
7689b9e5 |
508 | $query = ($query ? { '-and' => [ $cond, $query ] } : $cond); |
509 | $self->result_source->related_source($rel)->resultset->search( |
aa56106b |
510 | $query, $attrs |
511 | ); |
7689b9e5 |
512 | } |
30236e47 |
513 | }; |
514 | } |
515 | |
8091aa91 |
516 | =head2 search_related |
503536d5 |
517 | |
5b89a768 |
518 | @objects = $rs->search_related('relname', $cond, $attrs); |
519 | $objects_rs = $rs->search_related('relname', $cond, $attrs); |
30236e47 |
520 | |
521 | Run a search on a related resultset. The search will be restricted to the |
522 | item or items represented by the L<DBIx::Class::ResultSet> it was called |
523 | upon. This method can be called on a ResultSet, a Row or a ResultSource class. |
503536d5 |
524 | |
525 | =cut |
526 | |
55e2d745 |
527 | sub search_related { |
ff7bb7a1 |
528 | return shift->related_resultset(shift)->search(@_); |
b52e9bf8 |
529 | } |
530 | |
5b89a768 |
531 | =head2 search_related_rs |
532 | |
533 | ( $objects_rs ) = $rs->search_related_rs('relname', $cond, $attrs); |
534 | |
fd323bf1 |
535 | This method works exactly the same as search_related, except that |
48580715 |
536 | it guarantees a resultset, even in list context. |
5b89a768 |
537 | |
538 | =cut |
539 | |
540 | sub search_related_rs { |
541 | return shift->related_resultset(shift)->search_rs(@_); |
542 | } |
543 | |
b52e9bf8 |
544 | =head2 count_related |
545 | |
7be93b07 |
546 | $obj->count_related('relname', $cond, $attrs); |
b52e9bf8 |
547 | |
bc0c9800 |
548 | Returns the count of all the items in the related resultset, restricted by the |
549 | current item or where conditions. Can be called on a |
27f01d1f |
550 | L<DBIx::Class::Manual::Glossary/"ResultSet"> or a |
bc0c9800 |
551 | L<DBIx::Class::Manual::Glossary/"Row"> object. |
30236e47 |
552 | |
b52e9bf8 |
553 | =cut |
554 | |
555 | sub count_related { |
556 | my $self = shift; |
557 | return $self->search_related(@_)->count; |
55e2d745 |
558 | } |
559 | |
30236e47 |
560 | =head2 new_related |
561 | |
562 | my $new_obj = $obj->new_related('relname', \%col_data); |
563 | |
564 | Create a new item of the related foreign class. If called on a |
fd323bf1 |
565 | L<Row|DBIx::Class::Manual::Glossary/"Row"> object, it will magically |
566 | set any foreign key columns of the new object to the related primary |
567 | key columns of the source object for you. The newly created item will |
479b2a6a |
568 | not be saved into your storage until you call L<DBIx::Class::Row/insert> |
30236e47 |
569 | on it. |
570 | |
571 | =cut |
572 | |
573 | sub new_related { |
81e4dc3d |
574 | my ($self, $rel, $values) = @_; |
78b948c3 |
575 | |
576 | # FIXME - this is a bad position for this (also an identical copy in |
577 | # set_from_related), but I have no saner way to hook, and I absolutely |
578 | # want this to throw at least for coderefs, instead of the "insert a NULL |
579 | # when it gets hard" insanity --ribasushi |
580 | # |
581 | # sanity check - currently throw when a complex coderef rel is encountered |
582 | # FIXME - should THROW MOAR! |
583 | |
584 | if (ref $self) { # cdbi calls this as a class method, /me vomits |
585 | |
586 | my $rsrc = $self->result_source; |
587 | my (undef, $crosstable, $relcols) = $rsrc->_resolve_condition ( |
588 | $rsrc->relationship_info($rel)->{cond}, $rel, $self, $rel |
589 | ); |
590 | |
591 | $self->throw_exception("Custom relationship '$rel' does not resolve to a join-free condition fragment") |
592 | if $crosstable; |
593 | |
594 | if (@{$relcols || []} and @$relcols = grep { ! exists $values->{$_} } @$relcols) { |
595 | $self->throw_exception(sprintf ( |
596 | "Custom relationship '%s' not definitive - returns conditions instead of values for column(s): %s", |
597 | $rel, |
598 | map { "'$_'" } @$relcols |
599 | )); |
600 | } |
601 | } |
602 | |
81e4dc3d |
603 | return $self->search_related($rel)->new_result($values); |
30236e47 |
604 | } |
605 | |
8091aa91 |
606 | =head2 create_related |
503536d5 |
607 | |
30236e47 |
608 | my $new_obj = $obj->create_related('relname', \%col_data); |
609 | |
610 | Creates a new item, similarly to new_related, and also inserts the item's data |
611 | into your storage medium. See the distinction between C<create> and C<new> |
612 | in L<DBIx::Class::ResultSet> for details. |
503536d5 |
613 | |
614 | =cut |
615 | |
55e2d745 |
616 | sub create_related { |
3842b955 |
617 | my $self = shift; |
fea3d045 |
618 | my $rel = shift; |
78b948c3 |
619 | my $obj = $self->new_related($rel, @_)->insert; |
64acc2bc |
620 | delete $self->{related_resultsets}->{$rel}; |
621 | return $obj; |
55e2d745 |
622 | } |
623 | |
8091aa91 |
624 | =head2 find_related |
503536d5 |
625 | |
30236e47 |
626 | my $found_item = $obj->find_related('relname', @pri_vals | \%pri_vals); |
627 | |
628 | Attempt to find a related object using its primary key or unique constraints. |
27f01d1f |
629 | See L<DBIx::Class::ResultSet/find> for details. |
503536d5 |
630 | |
631 | =cut |
632 | |
1a14aa3f |
633 | sub find_related { |
634 | my $self = shift; |
635 | my $rel = shift; |
716b3d29 |
636 | return $self->search_related($rel)->find(@_); |
1a14aa3f |
637 | } |
638 | |
b3e1f1f5 |
639 | =head2 find_or_new_related |
640 | |
641 | my $new_obj = $obj->find_or_new_related('relname', \%col_data); |
642 | |
643 | Find an item of a related class. If none exists, instantiate a new item of the |
644 | related class. The object will not be saved into your storage until you call |
645 | L<DBIx::Class::Row/insert> on it. |
646 | |
647 | =cut |
648 | |
649 | sub find_or_new_related { |
650 | my $self = shift; |
e60dc79f |
651 | my $obj = $self->find_related(@_); |
652 | return defined $obj ? $obj : $self->new_related(@_); |
b3e1f1f5 |
653 | } |
654 | |
8091aa91 |
655 | =head2 find_or_create_related |
503536d5 |
656 | |
30236e47 |
657 | my $new_obj = $obj->find_or_create_related('relname', \%col_data); |
658 | |
27f01d1f |
659 | Find or create an item of a related class. See |
b3e1f1f5 |
660 | L<DBIx::Class::ResultSet/find_or_create> for details. |
503536d5 |
661 | |
662 | =cut |
663 | |
55e2d745 |
664 | sub find_or_create_related { |
665 | my $self = shift; |
9c2c91ea |
666 | my $obj = $self->find_related(@_); |
667 | return (defined($obj) ? $obj : $self->create_related(@_)); |
55e2d745 |
668 | } |
669 | |
045120e6 |
670 | =head2 update_or_create_related |
671 | |
672 | my $updated_item = $obj->update_or_create_related('relname', \%col_data, \%attrs?); |
673 | |
674 | Update or create an item of a related class. See |
f7e1846f |
675 | L<DBIx::Class::ResultSet/update_or_create> for details. |
045120e6 |
676 | |
677 | =cut |
678 | |
679 | sub update_or_create_related { |
680 | my $self = shift; |
681 | my $rel = shift; |
682 | return $self->related_resultset($rel)->update_or_create(@_); |
683 | } |
684 | |
8091aa91 |
685 | =head2 set_from_related |
503536d5 |
686 | |
30236e47 |
687 | $book->set_from_related('author', $author_obj); |
ac8e89d7 |
688 | $book->author($author_obj); ## same thing |
30236e47 |
689 | |
690 | Set column values on the current object, using related values from the given |
691 | related object. This is used to associate previously separate objects, for |
692 | example, to set the correct author for a book, find the Author object, then |
693 | call set_from_related on the book. |
694 | |
ac8e89d7 |
695 | This is called internally when you pass existing objects as values to |
48580715 |
696 | L<DBIx::Class::ResultSet/create>, or pass an object to a belongs_to accessor. |
ac8e89d7 |
697 | |
27f01d1f |
698 | The columns are only set in the local copy of the object, call L</update> to |
699 | set them in the storage. |
503536d5 |
700 | |
701 | =cut |
702 | |
55e2d745 |
703 | sub set_from_related { |
704 | my ($self, $rel, $f_obj) = @_; |
aa56106b |
705 | |
78b948c3 |
706 | my $rsrc = $self->result_source; |
707 | my $rel_info = $rsrc->relationship_info($rel) |
aa56106b |
708 | or $self->throw_exception( "No such relationship ${rel}" ); |
709 | |
2c037e6b |
710 | if (defined $f_obj) { |
164efde3 |
711 | my $f_class = $rel_info->{class}; |
2c037e6b |
712 | $self->throw_exception( "Object $f_obj isn't a ".$f_class ) |
6298a324 |
713 | unless blessed $f_obj and $f_obj->isa($f_class); |
2c037e6b |
714 | } |
a126983e |
715 | |
a126983e |
716 | |
78b948c3 |
717 | # FIXME - this is a bad position for this (also an identical copy in |
718 | # new_related), but I have no saner way to hook, and I absolutely |
719 | # want this to throw at least for coderefs, instead of the "insert a NULL |
720 | # when it gets hard" insanity --ribasushi |
721 | # |
722 | # sanity check - currently throw when a complex coderef rel is encountered |
723 | # FIXME - should THROW MOAR! |
724 | my ($cond, $crosstable, $relcols) = $rsrc->_resolve_condition ( |
725 | $rel_info->{cond}, $f_obj, $rel, $rel |
726 | ); |
727 | $self->throw_exception("Custom relationship '$rel' does not resolve to a join-free condition fragment") |
728 | if $crosstable; |
729 | $self->throw_exception(sprintf ( |
730 | "Custom relationship '%s' not definitive - returns conditions instead of values for column(s): %s", |
731 | $rel, |
732 | map { "'$_'" } @$relcols |
733 | )) if @{$relcols || []}; |
aa56106b |
734 | |
735 | $self->set_columns($cond); |
a126983e |
736 | |
55e2d745 |
737 | return 1; |
738 | } |
739 | |
8091aa91 |
740 | =head2 update_from_related |
503536d5 |
741 | |
30236e47 |
742 | $book->update_from_related('author', $author_obj); |
743 | |
27f01d1f |
744 | The same as L</"set_from_related">, but the changes are immediately updated |
745 | in storage. |
503536d5 |
746 | |
747 | =cut |
748 | |
55e2d745 |
749 | sub update_from_related { |
750 | my $self = shift; |
751 | $self->set_from_related(@_); |
752 | $self->update; |
753 | } |
754 | |
8091aa91 |
755 | =head2 delete_related |
503536d5 |
756 | |
30236e47 |
757 | $obj->delete_related('relname', $cond, $attrs); |
758 | |
759 | Delete any related item subject to the given conditions. |
503536d5 |
760 | |
761 | =cut |
762 | |
55e2d745 |
763 | sub delete_related { |
764 | my $self = shift; |
64acc2bc |
765 | my $obj = $self->search_related(@_)->delete; |
766 | delete $self->{related_resultsets}->{$_[0]}; |
767 | return $obj; |
55e2d745 |
768 | } |
769 | |
ec353f53 |
770 | =head2 add_to_$rel |
771 | |
772 | B<Currently only available for C<has_many>, C<many-to-many> and 'multi' type |
773 | relationships.> |
774 | |
775 | =over 4 |
776 | |
777 | =item Arguments: ($foreign_vals | $obj), $link_vals? |
778 | |
779 | =back |
780 | |
781 | my $role = $schema->resultset('Role')->find(1); |
782 | $actor->add_to_roles($role); |
783 | # creates a My::DBIC::Schema::ActorRoles linking table row object |
784 | |
785 | $actor->add_to_roles({ name => 'lead' }, { salary => 15_000_000 }); |
786 | # creates a new My::DBIC::Schema::Role row object and the linking table |
787 | # object with an extra column in the link |
788 | |
789 | Adds a linking table object for C<$obj> or C<$foreign_vals>. If the first |
790 | argument is a hash reference, the related object is created first with the |
791 | column values in the hash. If an object reference is given, just the linking |
792 | table object is created. In either case, any additional column values for the |
793 | linking table object can be specified in C<$link_vals>. |
794 | |
795 | =head2 set_$rel |
796 | |
797 | B<Currently only available for C<many-to-many> relationships.> |
798 | |
799 | =over 4 |
800 | |
ac36a402 |
801 | =item Arguments: (\@hashrefs | \@objs), $link_vals? |
ec353f53 |
802 | |
803 | =back |
804 | |
805 | my $actor = $schema->resultset('Actor')->find(1); |
fd323bf1 |
806 | my @roles = $schema->resultset('Role')->search({ role => |
debccec3 |
807 | { '-in' => ['Fred', 'Barney'] } } ); |
ec353f53 |
808 | |
4d3a827d |
809 | $actor->set_roles(\@roles); |
810 | # Replaces all of $actor's previous roles with the two named |
ec353f53 |
811 | |
ac36a402 |
812 | $actor->set_roles(\@roles, { salary => 15_000_000 }); |
813 | # Sets a column in the link table for all roles |
814 | |
815 | |
4d3a827d |
816 | Replace all the related objects with the given reference to a list of |
817 | objects. This does a C<delete> B<on the link table resultset> to remove the |
818 | association between the current object and all related objects, then calls |
819 | C<add_to_$rel> repeatedly to link all the new objects. |
bba68c67 |
820 | |
821 | Note that this means that this method will B<not> delete any objects in the |
822 | table on the right side of the relation, merely that it will delete the link |
823 | between them. |
ec353f53 |
824 | |
4d3a827d |
825 | Due to a mistake in the original implementation of this method, it will also |
826 | accept a list of objects or hash references. This is B<deprecated> and will be |
827 | removed in a future version. |
828 | |
ec353f53 |
829 | =head2 remove_from_$rel |
830 | |
831 | B<Currently only available for C<many-to-many> relationships.> |
832 | |
833 | =over 4 |
834 | |
835 | =item Arguments: $obj |
836 | |
837 | =back |
838 | |
839 | my $role = $schema->resultset('Role')->find(1); |
840 | $actor->remove_from_roles($role); |
841 | # removes $role's My::DBIC::Schema::ActorRoles linking table row object |
842 | |
843 | Removes the link between the current object and the related object. Note that |
844 | the related object itself won't be deleted unless you call ->delete() on |
845 | it. This method just removes the link between the two objects. |
846 | |
55e2d745 |
847 | =head1 AUTHORS |
848 | |
daec44b8 |
849 | Matt S. Trout <mst@shadowcatsystems.co.uk> |
55e2d745 |
850 | |
851 | =head1 LICENSE |
852 | |
853 | You may distribute this code under the same terms as Perl itself. |
854 | |
855 | =cut |
856 | |
4d87db01 |
857 | 1; |