Commit | Line | Data |
3b44ccc6 |
1 | =head1 NAME |
9c82c181 |
2 | |
40dbc108 |
3 | DBIx::Class::Manual::Cookbook - Miscellaneous recipes |
ee38fa40 |
4 | |
d2f3e87b |
5 | =head1 SEARCHING |
2913b2d3 |
6 | |
d2f3e87b |
7 | =head2 Paged results |
faf62551 |
8 | |
bade79c4 |
9 | When you expect a large number of results, you can ask L<DBIx::Class> for a |
264f1571 |
10 | paged resultset, which will fetch only a defined number of records at a time: |
faf62551 |
11 | |
bade79c4 |
12 | my $rs = $schema->resultset('Artist')->search( |
5e8b1b2a |
13 | undef, |
bade79c4 |
14 | { |
15 | page => 1, # page to return (defaults to 1) |
16 | rows => 10, # number of results per page |
17 | }, |
18 | ); |
faf62551 |
19 | |
bade79c4 |
20 | return $rs->all(); # all records for page 1 |
faf62551 |
21 | |
ec30560d |
22 | You can get a L<Data::Page> object for the resultset (suitable for use |
23 | in e.g. a template) using the C<pager> method: |
faf62551 |
24 | |
bade79c4 |
25 | return $rs->pager(); |
faf62551 |
26 | |
d2f3e87b |
27 | =head2 Complex WHERE clauses |
2913b2d3 |
28 | |
40dbc108 |
29 | Sometimes you need to formulate a query using specific operators: |
30 | |
ea6309e2 |
31 | my @albums = $schema->resultset('Album')->search({ |
35d4fe78 |
32 | artist => { 'like', '%Lamb%' }, |
33 | title => { 'like', '%Fear of Fours%' }, |
34 | }); |
40dbc108 |
35 | |
36 | This results in something like the following C<WHERE> clause: |
37 | |
35d4fe78 |
38 | WHERE artist LIKE '%Lamb%' AND title LIKE '%Fear of Fours%' |
40dbc108 |
39 | |
40 | Other queries might require slightly more complex logic: |
41 | |
ea6309e2 |
42 | my @albums = $schema->resultset('Album')->search({ |
35d4fe78 |
43 | -or => [ |
44 | -and => [ |
45 | artist => { 'like', '%Smashing Pumpkins%' }, |
46 | title => 'Siamese Dream', |
47 | ], |
48 | artist => 'Starchildren', |
49 | ], |
50 | }); |
40dbc108 |
51 | |
52 | This results in the following C<WHERE> clause: |
53 | |
35d4fe78 |
54 | WHERE ( artist LIKE '%Smashing Pumpkins%' AND title = 'Siamese Dream' ) |
55 | OR artist = 'Starchildren' |
40dbc108 |
56 | |
57 | For more information on generating complex queries, see |
58 | L<SQL::Abstract/WHERE CLAUSES>. |
ee38fa40 |
59 | |
b9823354 |
60 | =head2 Retrieve one and only one row from a resultset |
61 | |
62 | Sometimes you need only the first "top" row of a resultset. While this can be |
63 | easily done with L<< $rs->first|DBIx::Class::ResultSet/first >>, it is suboptimal, |
64 | as a full blown cursor for the resultset will be created and then immediately |
65 | destroyed after fetching the first row object. |
66 | L<< $rs->single|DBIx::Class::ResultSet/single >> is |
67 | designed specifically for this case - it will grab the first returned result |
68 | without even instantiating a cursor. |
69 | |
70 | Before replacing all your calls to C<first()> with C<single()> please observe the |
71 | following CAVEATS: |
72 | |
73 | =over |
74 | |
75 | =item * |
76 | While single() takes a search condition just like search() does, it does |
77 | _not_ accept search attributes. However one can always chain a single() to |
78 | a search(): |
79 | |
80 | my $top_cd = $cd_rs -> search({}, { order_by => 'rating' }) -> single; |
81 | |
82 | |
83 | =item * |
84 | Since single() is the engine behind find(), it is designed to fetch a |
85 | single row per database query. Thus a warning will be issued when the |
86 | underlying SELECT returns more than one row. Sometimes however this usage |
87 | is valid: i.e. we have an arbitrary number of cd's but only one of them is |
88 | at the top of the charts at any given time. If you know what you are doing, |
89 | you can silence the warning by explicitly limiting the resultset size: |
90 | |
91 | my $top_cd = $cd_rs -> search ({}, { order_by => 'rating', rows => 1 }) -> single; |
92 | |
93 | =back |
94 | |
d2f3e87b |
95 | =head2 Arbitrary SQL through a custom ResultSource |
321d9634 |
96 | |
97 | Sometimes you have to run arbitrary SQL because your query is too complex |
98 | (e.g. it contains Unions, Sub-Selects, Stored Procedures, etc.) or has to |
99 | be optimized for your database in a special way, but you still want to |
100 | get the results as a L<DBIx::Class::ResultSet>. |
101 | The recommended way to accomplish this is by defining a separate ResultSource |
102 | for your query. You can then inject complete SQL statements using a scalar |
103 | reference (this is a feature of L<SQL::Abstract>). |
104 | |
105 | Say you want to run a complex custom query on your user data, here's what |
106 | you have to add to your User class: |
107 | |
23471103 |
108 | package My::Schema::Result::User; |
321d9634 |
109 | |
110 | use base qw/DBIx::Class/; |
111 | |
112 | # ->load_components, ->table, ->add_columns, etc. |
113 | |
114 | # Make a new ResultSource based on the User class |
115 | my $source = __PACKAGE__->result_source_instance(); |
116 | my $new_source = $source->new( $source ); |
117 | $new_source->source_name( 'UserFriendsComplex' ); |
118 | |
119 | # Hand in your query as a scalar reference |
120 | # It will be added as a sub-select after FROM, |
121 | # so pay attention to the surrounding brackets! |
122 | $new_source->name( \<<SQL ); |
123 | ( SELECT u.* FROM user u |
124 | INNER JOIN user_friends f ON u.id = f.user_id |
125 | WHERE f.friend_user_id = ? |
126 | UNION |
127 | SELECT u.* FROM user u |
128 | INNER JOIN user_friends f ON u.id = f.friend_user_id |
129 | WHERE f.user_id = ? ) |
130 | SQL |
131 | |
132 | # Finally, register your new ResultSource with your Schema |
dbe79da9 |
133 | My::Schema->register_extra_source( 'UserFriendsComplex' => $new_source ); |
321d9634 |
134 | |
135 | Next, you can execute your complex query using bind parameters like this: |
136 | |
137 | my $friends = [ $schema->resultset( 'UserFriendsComplex' )->search( {}, |
138 | { |
139 | bind => [ 12345, 12345 ] |
140 | } |
141 | ) ]; |
142 | |
d00a5c68 |
143 | ... and you'll get back a perfect L<DBIx::Class::ResultSet> (except, of course, |
144 | that you cannot modify the rows it contains, ie. cannot call L</update>, |
145 | L</delete>, ... on it). |
146 | |
147 | If you prefer to have the definitions of these custom ResultSources in separate |
148 | files (instead of stuffing all of them into the same resultset class), you can |
149 | achieve the same with subclassing the resultset class and defining the |
150 | ResultSource there: |
151 | |
23471103 |
152 | package My::Schema::Result::UserFriendsComplex; |
d00a5c68 |
153 | |
23471103 |
154 | use My::Schema::Result::User; |
155 | use base qw/My::Schema::Result::User/; |
d00a5c68 |
156 | |
157 | __PACKAGE__->table('dummy'); # currently must be called before anything else |
158 | |
159 | # Hand in your query as a scalar reference |
160 | # It will be added as a sub-select after FROM, |
161 | # so pay attention to the surrounding brackets! |
162 | __PACKAGE__->name( \<<SQL ); |
163 | ( SELECT u.* FROM user u |
164 | INNER JOIN user_friends f ON u.id = f.user_id |
165 | WHERE f.friend_user_id = ? |
166 | UNION |
167 | SELECT u.* FROM user u |
168 | INNER JOIN user_friends f ON u.id = f.friend_user_id |
169 | WHERE f.user_id = ? ) |
170 | SQL |
171 | |
172 | TIMTOWDI. |
321d9634 |
173 | |
d2f3e87b |
174 | =head2 Using specific columns |
faf62551 |
175 | |
324572ca |
176 | When you only want specific columns from a table, you can use |
177 | C<columns> to specify which ones you need. This is useful to avoid |
178 | loading columns with large amounts of data that you aren't about to |
179 | use anyway: |
faf62551 |
180 | |
bade79c4 |
181 | my $rs = $schema->resultset('Artist')->search( |
5e8b1b2a |
182 | undef, |
bade79c4 |
183 | { |
5e8b1b2a |
184 | columns => [qw/ name /] |
bade79c4 |
185 | } |
186 | ); |
faf62551 |
187 | |
bade79c4 |
188 | # Equivalent SQL: |
189 | # SELECT artist.name FROM artist |
faf62551 |
190 | |
324572ca |
191 | This is a shortcut for C<select> and C<as>, see below. C<columns> |
192 | cannot be used together with C<select> and C<as>. |
193 | |
d2f3e87b |
194 | =head2 Using database functions or stored procedures |
faf62551 |
195 | |
bade79c4 |
196 | The combination of C<select> and C<as> can be used to return the result of a |
197 | database function or stored procedure as a column value. You use C<select> to |
198 | specify the source for your column value (e.g. a column name, function, or |
199 | stored procedure name). You then use C<as> to set the column name you will use |
200 | to access the returned value: |
faf62551 |
201 | |
bade79c4 |
202 | my $rs = $schema->resultset('Artist')->search( |
324572ca |
203 | {}, |
bade79c4 |
204 | { |
205 | select => [ 'name', { LENGTH => 'name' } ], |
206 | as => [qw/ name name_length /], |
207 | } |
208 | ); |
faf62551 |
209 | |
bade79c4 |
210 | # Equivalent SQL: |
98b65433 |
211 | # SELECT name name, LENGTH( name ) |
bade79c4 |
212 | # FROM artist |
faf62551 |
213 | |
d676881f |
214 | Note that the C< as > attribute has absolutely nothing to with the sql |
215 | syntax C< SELECT foo AS bar > (see the documentation in |
216 | L<DBIx::Class::ResultSet/ATTRIBUTES>). If your alias exists as a |
217 | column in your base class (i.e. it was added with C<add_columns>), you |
218 | just access it as normal. Our C<Artist> class has a C<name> column, so |
219 | we just use the C<name> accessor: |
faf62551 |
220 | |
bade79c4 |
221 | my $artist = $rs->first(); |
222 | my $name = $artist->name(); |
faf62551 |
223 | |
224 | If on the other hand the alias does not correspond to an existing column, you |
324572ca |
225 | have to fetch the value using the C<get_column> accessor: |
faf62551 |
226 | |
bade79c4 |
227 | my $name_length = $artist->get_column('name_length'); |
faf62551 |
228 | |
bade79c4 |
229 | If you don't like using C<get_column>, you can always create an accessor for |
faf62551 |
230 | any of your aliases using either of these: |
231 | |
bade79c4 |
232 | # Define accessor manually: |
233 | sub name_length { shift->get_column('name_length'); } |
faf62551 |
234 | |
bade79c4 |
235 | # Or use DBIx::Class::AccessorGroup: |
236 | __PACKAGE__->mk_group_accessors('column' => 'name_length'); |
faf62551 |
237 | |
d2f3e87b |
238 | =head2 SELECT DISTINCT with multiple columns |
faf62551 |
239 | |
58a20107 |
240 | my $rs = $schema->resultset('Artist')->search( |
324572ca |
241 | {}, |
bade79c4 |
242 | { |
cd87b928 |
243 | columns => [ qw/artist_id name rank/ ], |
58a20107 |
244 | distinct => 1 |
245 | } |
246 | ); |
247 | |
248 | my $rs = $schema->resultset('Artist')->search( |
249 | {}, |
250 | { |
cd87b928 |
251 | columns => [ qw/artist_id name rank/ ], |
252 | group_by => [ qw/artist_id name rank/ ], |
bade79c4 |
253 | } |
254 | ); |
faf62551 |
255 | |
58a20107 |
256 | # Equivalent SQL: |
cd87b928 |
257 | # SELECT me.artist_id, me.name, me.rank |
58a20107 |
258 | # FROM artist me |
cd87b928 |
259 | # GROUP BY artist_id, name, rank |
58a20107 |
260 | |
d2f3e87b |
261 | =head2 SELECT COUNT(DISTINCT colname) |
6607ee1b |
262 | |
58a20107 |
263 | my $rs = $schema->resultset('Artist')->search( |
324572ca |
264 | {}, |
bade79c4 |
265 | { |
58a20107 |
266 | columns => [ qw/name/ ], |
267 | distinct => 1 |
bade79c4 |
268 | } |
269 | ); |
6607ee1b |
270 | |
58a20107 |
271 | my $rs = $schema->resultset('Artist')->search( |
272 | {}, |
273 | { |
274 | columns => [ qw/name/ ], |
275 | group_by => [ qw/name/ ], |
276 | } |
277 | ); |
278 | |
279 | my $count = $rs->count; |
280 | |
281 | # Equivalent SQL: |
8935bae3 |
282 | # SELECT COUNT( * ) FROM (SELECT me.name FROM artist me GROUP BY me.name) count_subq: |
3d565896 |
283 | |
d2f3e87b |
284 | =head2 Grouping results |
bade79c4 |
285 | |
286 | L<DBIx::Class> supports C<GROUP BY> as follows: |
287 | |
288 | my $rs = $schema->resultset('Artist')->search( |
324572ca |
289 | {}, |
bade79c4 |
290 | { |
291 | join => [qw/ cds /], |
51458a6a |
292 | select => [ 'name', { count => 'cds.id' } ], |
bade79c4 |
293 | as => [qw/ name cd_count /], |
294 | group_by => [qw/ name /] |
295 | } |
296 | ); |
6607ee1b |
297 | |
bade79c4 |
298 | # Equivalent SQL: |
51458a6a |
299 | # SELECT name, COUNT( cd.id ) FROM artist |
300 | # LEFT JOIN cd ON artist.id = cd.artist |
bade79c4 |
301 | # GROUP BY name |
6607ee1b |
302 | |
d676881f |
303 | Please see L<DBIx::Class::ResultSet/ATTRIBUTES> documentation if you |
304 | are in any way unsure about the use of the attributes above (C< join |
305 | >, C< select >, C< as > and C< group_by >). |
306 | |
70bb942d |
307 | =head2 Subqueries (EXPERIMENTAL) |
03834f77 |
308 | |
309 | You can write subqueries relatively easily in DBIC. |
310 | |
311 | my $inside_rs = $schema->resultset('Artist')->search({ |
312 | name => [ 'Billy Joel', 'Brittany Spears' ], |
313 | }); |
314 | |
68a797c1 |
315 | my $rs = $schema->resultset('CD')->search({ |
03834f77 |
316 | artist_id => { 'IN' => $inside_rs->get_column('id')->as_query }, |
317 | }); |
318 | |
319 | The usual operators ( =, !=, IN, NOT IN, etc) are supported. |
320 | |
321 | B<NOTE>: You have to explicitly use '=' when doing an equality comparison. |
322 | The following will B<not> work: |
323 | |
68a797c1 |
324 | my $rs = $schema->resultset('CD')->search({ |
03834f77 |
325 | artist_id => $inside_rs->get_column('id')->as_query, |
326 | }); |
327 | |
0a62f675 |
328 | =head3 Support |
329 | |
330 | Subqueries are supported in the where clause (first hashref), and in the |
331 | from, select, and +select attributes. |
332 | |
68a797c1 |
333 | =head3 Correlated subqueries |
334 | |
335 | my $cdrs = $schema->resultset('CD'); |
336 | my $rs = $cdrs->search({ |
337 | year => { |
338 | '=' => $cdrs->search( |
cd87b928 |
339 | { artist_id => { '=' => \'me.artist_id' } }, |
68a797c1 |
340 | { alias => 'inner' } |
341 | )->get_column('year')->max_rs->as_query, |
342 | }, |
343 | }); |
344 | |
345 | That creates the following SQL: |
346 | |
347 | SELECT me.cdid, me.artist, me.title, me.year, me.genreid, me.single_track |
348 | FROM cd me |
349 | WHERE year = ( |
350 | SELECT MAX(inner.year) |
351 | FROM cd inner |
cd87b928 |
352 | WHERE artist_id = me.artist_id |
68a797c1 |
353 | ) |
354 | |
6a9530d1 |
355 | =head3 EXPERIMENTAL |
356 | |
357 | Please note that subqueries are considered an experimental feature. |
358 | |
d2f3e87b |
359 | =head2 Predefined searches |
74dc2edc |
360 | |
324572ca |
361 | You can write your own L<DBIx::Class::ResultSet> class by inheriting from it |
74dc2edc |
362 | and define often used searches as methods: |
363 | |
364 | package My::DBIC::ResultSet::CD; |
365 | use strict; |
366 | use warnings; |
367 | use base 'DBIx::Class::ResultSet'; |
368 | |
369 | sub search_cds_ordered { |
370 | my ($self) = @_; |
371 | |
372 | return $self->search( |
373 | {}, |
374 | { order_by => 'name DESC' }, |
375 | ); |
376 | } |
377 | |
378 | 1; |
379 | |
380 | To use your resultset, first tell DBIx::Class to create an instance of it |
381 | for you, in your My::DBIC::Schema::CD class: |
382 | |
9dc1bfce |
383 | # class definition as normal |
384 | __PACKAGE__->load_components(qw/ Core /); |
385 | __PACKAGE__->table('cd'); |
386 | |
387 | # tell DBIC to use the custom ResultSet class |
74dc2edc |
388 | __PACKAGE__->resultset_class('My::DBIC::ResultSet::CD'); |
389 | |
9dc1bfce |
390 | Note that C<resultset_class> must be called after C<load_components> and C<table>, or you will get errors about missing methods. |
391 | |
74dc2edc |
392 | Then call your new method in your code: |
393 | |
394 | my $ordered_cds = $schema->resultset('CD')->search_cds_ordered(); |
395 | |
d2f3e87b |
396 | =head2 Using SQL functions on the left hand side of a comparison |
1c133e22 |
397 | |
398 | Using SQL functions on the left hand side of a comparison is generally |
399 | not a good idea since it requires a scan of the entire table. However, |
400 | it can be accomplished with C<DBIx::Class> when necessary. |
401 | |
402 | If you do not have quoting on, simply include the function in your search |
403 | specification as you would any column: |
404 | |
405 | $rs->search({ 'YEAR(date_of_birth)' => 1979 }); |
406 | |
407 | With quoting on, or for a more portable solution, use the C<where> |
408 | attribute: |
409 | |
410 | $rs->search({}, { where => \'YEAR(date_of_birth) = 1979' }); |
411 | |
412 | =begin hidden |
413 | |
414 | (When the bind args ordering bug is fixed, this technique will be better |
415 | and can replace the one above.) |
416 | |
417 | With quoting on, or for a more portable solution, use the C<where> and |
418 | C<bind> attributes: |
419 | |
420 | $rs->search({}, { |
421 | where => \'YEAR(date_of_birth) = ?', |
422 | bind => [ 1979 ] |
423 | }); |
424 | |
425 | =end hidden |
426 | |
d2f3e87b |
427 | =head1 JOINS AND PREFETCHING |
428 | |
87980de7 |
429 | =head2 Using joins and prefetch |
430 | |
bade79c4 |
431 | You can use the C<join> attribute to allow searching on, or sorting your |
cd87b928 |
432 | results by, one or more columns in a related table. |
433 | |
434 | This requires that you have defined the L<DBIx::Class::Relationship>. For example : |
435 | |
436 | My::Schema::CD->has_many( artists => 'My::Schema::Artist', 'artist_id'); |
437 | |
438 | To return all CDs matching a particular artist name, you specify the name of the relationship ('artists'): |
ea6309e2 |
439 | |
bade79c4 |
440 | my $rs = $schema->resultset('CD')->search( |
441 | { |
cd87b928 |
442 | 'artists.name' => 'Bob Marley' |
bade79c4 |
443 | }, |
444 | { |
cd87b928 |
445 | join => 'artists', # join the artist table |
bade79c4 |
446 | } |
447 | ); |
448 | |
449 | # Equivalent SQL: |
450 | # SELECT cd.* FROM cd |
451 | # JOIN artist ON cd.artist = artist.id |
452 | # WHERE artist.name = 'Bob Marley' |
453 | |
cd87b928 |
454 | In that example both the join, and the condition use the relationship name rather than the table name |
455 | (see DBIx::Class::Manual::Joining for more details on aliasing ). |
456 | |
bade79c4 |
457 | If required, you can now sort on any column in the related tables by including |
cd87b928 |
458 | it in your C<order_by> attribute, (again using the aliased relation name rather than table name) : |
bade79c4 |
459 | |
460 | my $rs = $schema->resultset('CD')->search( |
461 | { |
cd87b928 |
462 | 'artists.name' => 'Bob Marley' |
bade79c4 |
463 | }, |
464 | { |
cd87b928 |
465 | join => 'artists', |
466 | order_by => [qw/ artists.name /] |
bade79c4 |
467 | } |
2f81ed0f |
468 | ); |
ea6309e2 |
469 | |
bade79c4 |
470 | # Equivalent SQL: |
471 | # SELECT cd.* FROM cd |
472 | # JOIN artist ON cd.artist = artist.id |
473 | # WHERE artist.name = 'Bob Marley' |
474 | # ORDER BY artist.name |
ea6309e2 |
475 | |
bade79c4 |
476 | Note that the C<join> attribute should only be used when you need to search or |
477 | sort using columns in a related table. Joining related tables when you only |
478 | need columns from the main table will make performance worse! |
ea6309e2 |
479 | |
bade79c4 |
480 | Now let's say you want to display a list of CDs, each with the name of the |
481 | artist. The following will work fine: |
ea6309e2 |
482 | |
bade79c4 |
483 | while (my $cd = $rs->next) { |
484 | print "CD: " . $cd->title . ", Artist: " . $cd->artist->name; |
485 | } |
ea6309e2 |
486 | |
bade79c4 |
487 | There is a problem however. We have searched both the C<cd> and C<artist> tables |
488 | in our main query, but we have only returned data from the C<cd> table. To get |
489 | the artist name for any of the CD objects returned, L<DBIx::Class> will go back |
490 | to the database: |
ea6309e2 |
491 | |
bade79c4 |
492 | SELECT artist.* FROM artist WHERE artist.id = ? |
ea6309e2 |
493 | |
494 | A statement like the one above will run for each and every CD returned by our |
495 | main query. Five CDs, five extra queries. A hundred CDs, one hundred extra |
496 | queries! |
497 | |
bade79c4 |
498 | Thankfully, L<DBIx::Class> has a C<prefetch> attribute to solve this problem. |
897342e4 |
499 | This allows you to fetch results from related tables in advance: |
ea6309e2 |
500 | |
bade79c4 |
501 | my $rs = $schema->resultset('CD')->search( |
502 | { |
cd87b928 |
503 | 'artists.name' => 'Bob Marley' |
bade79c4 |
504 | }, |
505 | { |
cd87b928 |
506 | join => 'artists', |
507 | order_by => [qw/ artists.name /], |
508 | prefetch => 'artists' # return artist data too! |
bade79c4 |
509 | } |
510 | ); |
ea6309e2 |
511 | |
bade79c4 |
512 | # Equivalent SQL (note SELECT from both "cd" and "artist"): |
513 | # SELECT cd.*, artist.* FROM cd |
514 | # JOIN artist ON cd.artist = artist.id |
515 | # WHERE artist.name = 'Bob Marley' |
516 | # ORDER BY artist.name |
ea6309e2 |
517 | |
518 | The code to print the CD list remains the same: |
519 | |
bade79c4 |
520 | while (my $cd = $rs->next) { |
521 | print "CD: " . $cd->title . ", Artist: " . $cd->artist->name; |
522 | } |
ea6309e2 |
523 | |
bade79c4 |
524 | L<DBIx::Class> has now prefetched all matching data from the C<artist> table, |
ea6309e2 |
525 | so no additional SQL statements are executed. You now have a much more |
526 | efficient query. |
527 | |
bade79c4 |
528 | Also note that C<prefetch> should only be used when you know you will |
ea6309e2 |
529 | definitely use data from a related table. Pre-fetching related tables when you |
530 | only need columns from the main table will make performance worse! |
531 | |
51458a6a |
532 | =head2 Multiple joins |
533 | |
534 | In the examples above, the C<join> attribute was a scalar. If you |
535 | pass an array reference instead, you can join to multiple tables. In |
536 | this example, we want to limit the search further, using |
537 | C<LinerNotes>: |
538 | |
539 | # Relationships defined elsewhere: |
540 | # CD->belongs_to('artist' => 'Artist'); |
541 | # CD->has_one('liner_notes' => 'LinerNotes', 'cd'); |
542 | my $rs = $schema->resultset('CD')->search( |
543 | { |
544 | 'artist.name' => 'Bob Marley' |
545 | 'liner_notes.notes' => { 'like', '%some text%' }, |
546 | }, |
547 | { |
548 | join => [qw/ artist liner_notes /], |
549 | order_by => [qw/ artist.name /], |
550 | } |
551 | ); |
552 | |
553 | # Equivalent SQL: |
554 | # SELECT cd.*, artist.*, liner_notes.* FROM cd |
555 | # JOIN artist ON cd.artist = artist.id |
556 | # JOIN liner_notes ON cd.id = liner_notes.cd |
557 | # WHERE artist.name = 'Bob Marley' |
558 | # ORDER BY artist.name |
559 | |
d2f3e87b |
560 | =head2 Multi-step joins |
ea6309e2 |
561 | |
562 | Sometimes you want to join more than one relationship deep. In this example, |
bade79c4 |
563 | we want to find all C<Artist> objects who have C<CD>s whose C<LinerNotes> |
564 | contain a specific string: |
565 | |
566 | # Relationships defined elsewhere: |
567 | # Artist->has_many('cds' => 'CD', 'artist'); |
568 | # CD->has_one('liner_notes' => 'LinerNotes', 'cd'); |
569 | |
570 | my $rs = $schema->resultset('Artist')->search( |
571 | { |
572 | 'liner_notes.notes' => { 'like', '%some text%' }, |
573 | }, |
574 | { |
575 | join => { |
576 | 'cds' => 'liner_notes' |
577 | } |
578 | } |
579 | ); |
ea6309e2 |
580 | |
bade79c4 |
581 | # Equivalent SQL: |
582 | # SELECT artist.* FROM artist |
51458a6a |
583 | # LEFT JOIN cd ON artist.id = cd.artist |
584 | # LEFT JOIN liner_notes ON cd.id = liner_notes.cd |
bade79c4 |
585 | # WHERE liner_notes.notes LIKE '%some text%' |
ea6309e2 |
586 | |
587 | Joins can be nested to an arbitrary level. So if we decide later that we |
588 | want to reduce the number of Artists returned based on who wrote the liner |
589 | notes: |
590 | |
bade79c4 |
591 | # Relationship defined elsewhere: |
592 | # LinerNotes->belongs_to('author' => 'Person'); |
593 | |
594 | my $rs = $schema->resultset('Artist')->search( |
595 | { |
596 | 'liner_notes.notes' => { 'like', '%some text%' }, |
597 | 'author.name' => 'A. Writer' |
598 | }, |
599 | { |
600 | join => { |
601 | 'cds' => { |
602 | 'liner_notes' => 'author' |
ea6309e2 |
603 | } |
bade79c4 |
604 | } |
605 | } |
606 | ); |
ea6309e2 |
607 | |
bade79c4 |
608 | # Equivalent SQL: |
609 | # SELECT artist.* FROM artist |
51458a6a |
610 | # LEFT JOIN cd ON artist.id = cd.artist |
611 | # LEFT JOIN liner_notes ON cd.id = liner_notes.cd |
612 | # LEFT JOIN author ON author.id = liner_notes.author |
bade79c4 |
613 | # WHERE liner_notes.notes LIKE '%some text%' |
614 | # AND author.name = 'A. Writer' |
87980de7 |
615 | |
51458a6a |
616 | =head2 Multi-step and multiple joins |
617 | |
618 | With various combinations of array and hash references, you can join |
619 | tables in any combination you desire. For example, to join Artist to |
620 | CD and Concert, and join CD to LinerNotes: |
621 | |
622 | # Relationships defined elsewhere: |
623 | # Artist->has_many('concerts' => 'Concert', 'artist'); |
624 | |
625 | my $rs = $schema->resultset('Artist')->search( |
626 | { }, |
627 | { |
628 | join => [ |
629 | { |
630 | cds => 'liner_notes' |
631 | }, |
632 | 'concerts' |
633 | ], |
634 | } |
635 | ); |
636 | |
637 | # Equivalent SQL: |
638 | # SELECT artist.* FROM artist |
639 | # LEFT JOIN cd ON artist.id = cd.artist |
640 | # LEFT JOIN liner_notes ON cd.id = liner_notes.cd |
641 | # LEFT JOIN concert ON artist.id = concert.artist |
642 | |
897342e4 |
643 | =head2 Multi-step prefetch |
644 | |
d76788de |
645 | C<prefetch> can be nested more than one relationship |
897342e4 |
646 | deep using the same syntax as a multi-step join: |
647 | |
648 | my $rs = $schema->resultset('Tag')->search( |
ac2803ef |
649 | {}, |
897342e4 |
650 | { |
651 | prefetch => { |
652 | cd => 'artist' |
653 | } |
654 | } |
655 | ); |
656 | |
657 | # Equivalent SQL: |
658 | # SELECT tag.*, cd.*, artist.* FROM tag |
51458a6a |
659 | # JOIN cd ON tag.cd = cd.id |
660 | # JOIN artist ON cd.artist = artist.id |
897342e4 |
661 | |
662 | Now accessing our C<cd> and C<artist> relationships does not need additional |
663 | SQL statements: |
664 | |
665 | my $tag = $rs->first; |
666 | print $tag->cd->artist->name; |
667 | |
d2f3e87b |
668 | =head1 ROW-LEVEL OPERATIONS |
669 | |
670 | =head2 Retrieving a row object's Schema |
671 | |
672 | It is possible to get a Schema object from a row object like so: |
673 | |
674 | my $schema = $cd->result_source->schema; |
675 | # use the schema as normal: |
676 | my $artist_rs = $schema->resultset('Artist'); |
677 | |
678 | This can be useful when you don't want to pass around a Schema object to every |
679 | method. |
680 | |
681 | =head2 Getting the value of the primary key for the last database insert |
682 | |
683 | AKA getting last_insert_id |
684 | |
d76788de |
685 | Thanks to the core component PK::Auto, this is straightforward: |
d2f3e87b |
686 | |
687 | my $foo = $rs->create(\%blah); |
688 | # do more stuff |
689 | my $id = $foo->id; # foo->my_primary_key_field will also work. |
690 | |
691 | If you are not using autoincrementing primary keys, this will probably |
692 | not work, but then you already know the value of the last primary key anyway. |
693 | |
694 | =head2 Stringification |
695 | |
696 | Employ the standard stringification technique by using the C<overload> |
697 | module. |
698 | |
699 | To make an object stringify itself as a single column, use something |
b24d86a1 |
700 | like this (replace C<name> with the column/method of your choice): |
d2f3e87b |
701 | |
702 | use overload '""' => sub { shift->name}, fallback => 1; |
703 | |
704 | For more complex stringification, you can use an anonymous subroutine: |
705 | |
706 | use overload '""' => sub { $_[0]->name . ", " . |
707 | $_[0]->address }, fallback => 1; |
708 | |
709 | =head3 Stringification Example |
710 | |
711 | Suppose we have two tables: C<Product> and C<Category>. The table |
712 | specifications are: |
713 | |
714 | Product(id, Description, category) |
715 | Category(id, Description) |
716 | |
717 | C<category> is a foreign key into the Category table. |
718 | |
719 | If you have a Product object C<$obj> and write something like |
720 | |
721 | print $obj->category |
722 | |
723 | things will not work as expected. |
724 | |
725 | To obtain, for example, the category description, you should add this |
726 | method to the class defining the Category table: |
727 | |
728 | use overload "" => sub { |
729 | my $self = shift; |
730 | |
731 | return $self->Description; |
732 | }, fallback => 1; |
733 | |
734 | =head2 Want to know if find_or_create found or created a row? |
735 | |
736 | Just use C<find_or_new> instead, then check C<in_storage>: |
737 | |
738 | my $obj = $rs->find_or_new({ blah => 'blarg' }); |
739 | unless ($obj->in_storage) { |
740 | $obj->insert; |
741 | # do whatever else you wanted if it was a new row |
742 | } |
743 | |
6fc80947 |
744 | =head2 Static sub-classing DBIx::Class result classes |
745 | |
746 | AKA adding additional relationships/methods/etc. to a model for a |
747 | specific usage of the (shared) model. |
748 | |
749 | B<Schema definition> |
750 | |
751 | package My::App::Schema; |
752 | |
753 | use base DBIx::Class::Schema; |
754 | |
755 | # load subclassed classes from My::App::Schema::Result/ResultSet |
756 | __PACKAGE__->load_namespaces; |
757 | |
758 | # load classes from shared model |
759 | load_classes({ |
760 | 'My::Shared::Model::Result' => [qw/ |
761 | Foo |
762 | Bar |
763 | /]}); |
764 | |
765 | 1; |
766 | |
767 | B<Result-Subclass definition> |
768 | |
769 | package My::App::Schema::Result::Baz; |
770 | |
771 | use strict; |
772 | use warnings; |
773 | use base My::Shared::Model::Result::Baz; |
774 | |
775 | # WARNING: Make sure you call table() again in your subclass, |
776 | # otherwise DBIx::Class::ResultSourceProxy::Table will not be called |
777 | # and the class name is not correctly registered as a source |
778 | __PACKAGE__->table('baz'); |
779 | |
780 | sub additional_method { |
781 | return "I'm an additional method only needed by this app"; |
782 | } |
783 | |
784 | 1; |
785 | |
d2f3e87b |
786 | =head2 Dynamic Sub-classing DBIx::Class proxy classes |
787 | |
788 | AKA multi-class object inflation from one table |
789 | |
790 | L<DBIx::Class> classes are proxy classes, therefore some different |
791 | techniques need to be employed for more than basic subclassing. In |
792 | this example we have a single user table that carries a boolean bit |
793 | for admin. We would like like to give the admin users |
794 | objects(L<DBIx::Class::Row>) the same methods as a regular user but |
795 | also special admin only methods. It doesn't make sense to create two |
796 | seperate proxy-class files for this. We would be copying all the user |
797 | methods into the Admin class. There is a cleaner way to accomplish |
798 | this. |
799 | |
800 | Overriding the C<inflate_result> method within the User proxy-class |
801 | gives us the effect we want. This method is called by |
802 | L<DBIx::Class::ResultSet> when inflating a result from storage. So we |
803 | grab the object being returned, inspect the values we are looking for, |
804 | bless it if it's an admin object, and then return it. See the example |
805 | below: |
806 | |
807 | B<Schema Definition> |
808 | |
23471103 |
809 | package My::Schema; |
d2f3e87b |
810 | |
811 | use base qw/DBIx::Class::Schema/; |
812 | |
6fc80947 |
813 | __PACKAGE__->load_namespaces; |
814 | |
815 | 1; |
d2f3e87b |
816 | |
817 | |
818 | B<Proxy-Class definitions> |
819 | |
23471103 |
820 | package My::Schema::Result::User; |
d2f3e87b |
821 | |
822 | use strict; |
823 | use warnings; |
824 | use base qw/DBIx::Class/; |
825 | |
826 | ### Defined what our admin class is for ensure_class_loaded |
827 | my $admin_class = __PACKAGE__ . '::Admin'; |
828 | |
829 | __PACKAGE__->load_components(qw/Core/); |
830 | |
831 | __PACKAGE__->table('users'); |
832 | |
833 | __PACKAGE__->add_columns(qw/user_id email password |
834 | firstname lastname active |
835 | admin/); |
836 | |
837 | __PACKAGE__->set_primary_key('user_id'); |
838 | |
839 | sub inflate_result { |
840 | my $self = shift; |
841 | my $ret = $self->next::method(@_); |
842 | if( $ret->admin ) {### If this is an admin rebless for extra functions |
843 | $self->ensure_class_loaded( $admin_class ); |
844 | bless $ret, $admin_class; |
845 | } |
846 | return $ret; |
847 | } |
848 | |
849 | sub hello { |
850 | print "I am a regular user.\n"; |
851 | return ; |
852 | } |
6fc80947 |
853 | |
854 | 1; |
855 | |
d2f3e87b |
856 | |
23471103 |
857 | package My::Schema::Result::User::Admin; |
d2f3e87b |
858 | |
859 | use strict; |
860 | use warnings; |
23471103 |
861 | use base qw/My::Schema::Result::User/; |
04d29efe |
862 | |
863 | # This line is important |
864 | __PACKAGE__->table('users'); |
d2f3e87b |
865 | |
866 | sub hello |
867 | { |
868 | print "I am an admin.\n"; |
869 | return; |
870 | } |
871 | |
872 | sub do_admin_stuff |
873 | { |
874 | print "I am doing admin stuff\n"; |
875 | return ; |
6fc80947 |
876 | } |
877 | |
878 | 1; |
d2f3e87b |
879 | |
880 | B<Test File> test.pl |
881 | |
882 | use warnings; |
883 | use strict; |
23471103 |
884 | use My::Schema; |
d2f3e87b |
885 | |
886 | my $user_data = { email => 'someguy@place.com', |
887 | password => 'pass1', |
888 | admin => 0 }; |
889 | |
890 | my $admin_data = { email => 'someadmin@adminplace.com', |
891 | password => 'pass2', |
892 | admin => 1 }; |
893 | |
23471103 |
894 | my $schema = My::Schema->connection('dbi:Pg:dbname=test'); |
d2f3e87b |
895 | |
896 | $schema->resultset('User')->create( $user_data ); |
897 | $schema->resultset('User')->create( $admin_data ); |
898 | |
899 | ### Now we search for them |
900 | my $user = $schema->resultset('User')->single( $user_data ); |
901 | my $admin = $schema->resultset('User')->single( $admin_data ); |
902 | |
903 | print ref $user, "\n"; |
904 | print ref $admin, "\n"; |
905 | |
906 | print $user->password , "\n"; # pass1 |
907 | print $admin->password , "\n";# pass2; inherited from User |
908 | print $user->hello , "\n";# I am a regular user. |
909 | print $admin->hello, "\n";# I am an admin. |
910 | |
911 | ### The statement below will NOT print |
912 | print "I can do admin stuff\n" if $user->can('do_admin_stuff'); |
913 | ### The statement below will print |
914 | print "I can do admin stuff\n" if $admin->can('do_admin_stuff'); |
915 | |
a5b29361 |
916 | =head2 Skip row object creation for faster results |
d2f3e87b |
917 | |
918 | DBIx::Class is not built for speed, it's built for convenience and |
919 | ease of use, but sometimes you just need to get the data, and skip the |
920 | fancy objects. |
921 | |
922 | To do this simply use L<DBIx::Class::ResultClass::HashRefInflator>. |
923 | |
924 | my $rs = $schema->resultset('CD'); |
925 | |
926 | $rs->result_class('DBIx::Class::ResultClass::HashRefInflator'); |
927 | |
928 | my $hash_ref = $rs->find(1); |
a5b29361 |
929 | |
d2f3e87b |
930 | Wasn't that easy? |
bc96f260 |
931 | |
db2b2eb6 |
932 | Beware, changing the Result class using |
933 | L<DBIx::Class::ResultSet/result_class> will replace any existing class |
934 | completely including any special components loaded using |
935 | load_components, eg L<DBIx::Class::InflateColumn::DateTime>. |
936 | |
d2f3e87b |
937 | =head2 Get raw data for blindingly fast results |
938 | |
939 | If the L<HashRefInflator|DBIx::Class::ResultClass::HashRefInflator> solution |
940 | above is not fast enough for you, you can use a DBIx::Class to return values |
db2b2eb6 |
941 | exactly as they come out of the database with none of the convenience methods |
d2f3e87b |
942 | wrapped round them. |
943 | |
2d7d8459 |
944 | This is used like so: |
d2f3e87b |
945 | |
946 | my $cursor = $rs->cursor |
947 | while (my @vals = $cursor->next) { |
948 | # use $val[0..n] here |
949 | } |
950 | |
951 | You will need to map the array offsets to particular columns (you can |
db2b2eb6 |
952 | use the L<DBIx::Class::ResultSet/select> attribute of L<DBIx::Class::ResultSet/search> to force ordering). |
d2f3e87b |
953 | |
954 | =head1 RESULTSET OPERATIONS |
955 | |
956 | =head2 Getting Schema from a ResultSet |
957 | |
db2b2eb6 |
958 | To get the L<DBIx::Class::Schema> object from a ResultSet, do the following: |
d2f3e87b |
959 | |
960 | $rs->result_source->schema |
961 | |
962 | =head2 Getting Columns Of Data |
963 | |
964 | AKA Aggregating Data |
ac2803ef |
965 | |
966 | If you want to find the sum of a particular column there are several |
967 | ways, the obvious one is to use search: |
968 | |
969 | my $rs = $schema->resultset('Items')->search( |
970 | {}, |
971 | { |
972 | select => [ { sum => 'Cost' } ], |
d676881f |
973 | as => [ 'total_cost' ], # remember this 'as' is for DBIx::Class::ResultSet not SQL |
ac2803ef |
974 | } |
975 | ); |
976 | my $tc = $rs->first->get_column('total_cost'); |
977 | |
978 | Or, you can use the L<DBIx::Class::ResultSetColumn>, which gets |
979 | returned when you ask the C<ResultSet> for a column using |
980 | C<get_column>: |
981 | |
982 | my $cost = $schema->resultset('Items')->get_column('Cost'); |
983 | my $tc = $cost->sum; |
984 | |
985 | With this you can also do: |
986 | |
987 | my $minvalue = $cost->min; |
988 | my $maxvalue = $cost->max; |
989 | |
990 | Or just iterate through the values of this column only: |
991 | |
992 | while ( my $c = $cost->next ) { |
993 | print $c; |
994 | } |
995 | |
996 | foreach my $c ($cost->all) { |
997 | print $c; |
998 | } |
999 | |
709353af |
1000 | C<ResultSetColumn> only has a limited number of built-in functions, if |
1001 | you need one that it doesn't have, then you can use the C<func> method |
1002 | instead: |
1003 | |
1004 | my $avg = $cost->func('AVERAGE'); |
1005 | |
1006 | This will cause the following SQL statement to be run: |
1007 | |
1008 | SELECT AVERAGE(Cost) FROM Items me |
1009 | |
1010 | Which will of course only work if your database supports this function. |
ac2803ef |
1011 | See L<DBIx::Class::ResultSetColumn> for more documentation. |
1012 | |
204e5c03 |
1013 | =head2 Creating a result set from a set of rows |
1014 | |
1015 | Sometimes you have a (set of) row objects that you want to put into a |
1016 | resultset without the need to hit the DB again. You can do that by using the |
1017 | L<set_cache|DBIx::Class::Resultset/set_cache> method: |
1018 | |
2d7a4e46 |
1019 | my @uploadable_groups; |
204e5c03 |
1020 | while (my $group = $groups->next) { |
1021 | if ($group->can_upload($self)) { |
1022 | push @uploadable_groups, $group; |
1023 | } |
1024 | } |
1025 | my $new_rs = $self->result_source->resultset; |
1026 | $new_rs->set_cache(\@uploadable_groups); |
1027 | return $new_rs; |
1028 | |
1029 | |
d2f3e87b |
1030 | =head1 USING RELATIONSHIPS |
acee4e4d |
1031 | |
d2f3e87b |
1032 | =head2 Create a new row in a related table |
acee4e4d |
1033 | |
6f1434fd |
1034 | my $author = $book->create_related('author', { name => 'Fred'}); |
acee4e4d |
1035 | |
d2f3e87b |
1036 | =head2 Search in a related table |
acee4e4d |
1037 | |
1038 | Only searches for books named 'Titanic' by the author in $author. |
1039 | |
6f1434fd |
1040 | my $books_rs = $author->search_related('books', { name => 'Titanic' }); |
acee4e4d |
1041 | |
d2f3e87b |
1042 | =head2 Delete data in a related table |
acee4e4d |
1043 | |
1044 | Deletes only the book named Titanic by the author in $author. |
1045 | |
6f1434fd |
1046 | $author->delete_related('books', { name => 'Titanic' }); |
acee4e4d |
1047 | |
d2f3e87b |
1048 | =head2 Ordering a relationship result set |
f8bad769 |
1049 | |
1050 | If you always want a relation to be ordered, you can specify this when you |
1051 | create the relationship. |
1052 | |
6f1434fd |
1053 | To order C<< $book->pages >> by descending page_number, create the relation |
1054 | as follows: |
f8bad769 |
1055 | |
6f1434fd |
1056 | __PACKAGE__->has_many('pages' => 'Page', 'book', { order_by => \'page_number DESC'} ); |
f8bad769 |
1057 | |
7c0825ab |
1058 | =head2 Filtering a relationship result set |
1059 | |
1060 | If you want to get a filtered result set, you can just add add to $attr as follows: |
1061 | |
1062 | __PACKAGE__->has_many('pages' => 'Page', 'book', { where => { scrap => 0 } } ); |
1063 | |
d2f3e87b |
1064 | =head2 Many-to-many relationships |
f8bad769 |
1065 | |
d2f3e87b |
1066 | This is straightforward using L<ManyToMany|DBIx::Class::Relationship/many_to_many>: |
f8bad769 |
1067 | |
d2f3e87b |
1068 | package My::User; |
6f1434fd |
1069 | use base 'DBIx::Class'; |
1070 | __PACKAGE__->load_components('Core'); |
d2f3e87b |
1071 | __PACKAGE__->table('user'); |
1072 | __PACKAGE__->add_columns(qw/id name/); |
1073 | __PACKAGE__->set_primary_key('id'); |
1074 | __PACKAGE__->has_many('user_address' => 'My::UserAddress', 'user'); |
1075 | __PACKAGE__->many_to_many('addresses' => 'user_address', 'address'); |
87980de7 |
1076 | |
d2f3e87b |
1077 | package My::UserAddress; |
6f1434fd |
1078 | use base 'DBIx::Class'; |
1079 | __PACKAGE__->load_components('Core'); |
d2f3e87b |
1080 | __PACKAGE__->table('user_address'); |
1081 | __PACKAGE__->add_columns(qw/user address/); |
1082 | __PACKAGE__->set_primary_key(qw/user address/); |
1083 | __PACKAGE__->belongs_to('user' => 'My::User'); |
1084 | __PACKAGE__->belongs_to('address' => 'My::Address'); |
181a28f4 |
1085 | |
d2f3e87b |
1086 | package My::Address; |
6f1434fd |
1087 | use base 'DBIx::Class'; |
1088 | __PACKAGE__->load_components('Core'); |
d2f3e87b |
1089 | __PACKAGE__->table('address'); |
1090 | __PACKAGE__->add_columns(qw/id street town area_code country/); |
1091 | __PACKAGE__->set_primary_key('id'); |
1092 | __PACKAGE__->has_many('user_address' => 'My::UserAddress', 'address'); |
1093 | __PACKAGE__->many_to_many('users' => 'user_address', 'user'); |
1094 | |
1095 | $rs = $user->addresses(); # get all addresses for a user |
1096 | $rs = $address->users(); # get all users for an address |
1097 | |
db2b2eb6 |
1098 | =head2 Relationships across DB schemas |
1099 | |
1100 | Mapping relationships across L<DB schemas|DBIx::Class::Manual::Glossary/DB schema> |
1101 | is easy as long as the schemas themselves are all accessible via the same DBI |
1102 | connection. In most cases, this means that they are on the same database host |
1103 | as each other and your connecting database user has the proper permissions to them. |
1104 | |
1105 | To accomplish this one only needs to specify the DB schema name in the table |
1106 | declaration, like so... |
1107 | |
1108 | package MyDatabase::Main::Artist; |
1109 | use base qw/DBIx::Class/; |
1110 | __PACKAGE__->load_components(qw/PK::Auto Core/); |
1111 | |
1112 | __PACKAGE__->table('database1.artist'); # will use "database1.artist" in FROM clause |
1113 | |
cd87b928 |
1114 | __PACKAGE__->add_columns(qw/ artist_id name /); |
1115 | __PACKAGE__->set_primary_key('artist_id'); |
db2b2eb6 |
1116 | __PACKAGE__->has_many('cds' => 'MyDatabase::Main::Cd'); |
1117 | |
1118 | 1; |
1119 | |
1120 | Whatever string you specify there will be used to build the "FROM" clause in SQL |
1121 | queries. |
1122 | |
1123 | The big drawback to this is you now have DB schema names hardcoded in your |
1124 | class files. This becomes especially troublesome if you have multiple instances |
1125 | of your application to support a change lifecycle (e.g. DEV, TEST, PROD) and |
1126 | the DB schemas are named based on the environment (e.g. database1_dev). |
1127 | |
1128 | However, one can dynamically "map" to the proper DB schema by overriding the |
1129 | L<connection|DBIx::Class::Schama/connection> method in your Schema class and |
1130 | building a renaming facility, like so: |
1131 | |
1132 | package MyDatabase::Schema; |
1133 | use Moose; |
1134 | |
1135 | extends 'DBIx::Class::Schema'; |
1136 | |
1137 | around connection => sub { |
1138 | my ( $inner, $self, $dsn, $username, $pass, $attr ) = ( shift, @_ ); |
1139 | |
1140 | my $postfix = delete $attr->{schema_name_postfix}; |
1141 | |
1142 | $inner->(@_); |
1143 | |
1144 | if ( $postfix ) { |
1145 | $self->append_db_name($postfix); |
1146 | } |
1147 | }; |
1148 | |
1149 | sub append_db_name { |
1150 | my ( $self, $postfix ) = @_; |
1151 | |
1152 | my @sources_with_db |
1153 | = grep |
1154 | { $_->name =~ /^\w+\./mx } |
1155 | map |
1156 | { $self->source($_) } |
1157 | $self->sources; |
1158 | |
1159 | foreach my $source (@sources_with_db) { |
1160 | my $name = $source->name; |
1161 | $name =~ s{^(\w+)\.}{${1}${postfix}\.}mx; |
1162 | |
1163 | $source->name($name); |
1164 | } |
1165 | } |
1166 | |
1167 | 1; |
1168 | |
1169 | By overridding the L<connection|DBIx::Class::Schama/connection> |
1170 | method and extracting a custom option from the provided \%attr hashref one can |
1171 | then simply iterate over all the Schema's ResultSources, renaming them as |
1172 | needed. |
1173 | |
1174 | To use this facility, simply add or modify the \%attr hashref that is passed to |
1175 | L<connection|DBIx::Class::Schama/connect>, as follows: |
1176 | |
1177 | my $schema |
1178 | = MyDatabase::Schema->connect( |
1179 | $dsn, |
1180 | $user, |
1181 | $pass, |
1182 | { |
1183 | schema_name_postfix => '_dev' |
1184 | # ... Other options as desired ... |
1185 | }) |
1186 | |
1187 | Obviously, one could accomplish even more advanced mapping via a hash map or a |
1188 | callback routine. |
1189 | |
d2f3e87b |
1190 | =head1 TRANSACTIONS |
1191 | |
1192 | As of version 0.04001, there is improved transaction support in |
1193 | L<DBIx::Class::Storage> and L<DBIx::Class::Schema>. Here is an |
1194 | example of the recommended way to use it: |
1195 | |
1196 | my $genus = $schema->resultset('Genus')->find(12); |
1197 | |
1198 | my $coderef2 = sub { |
1199 | $genus->extinct(1); |
1200 | $genus->update; |
1201 | }; |
70634260 |
1202 | |
181a28f4 |
1203 | my $coderef1 = sub { |
35d4fe78 |
1204 | $genus->add_to_species({ name => 'troglodyte' }); |
1205 | $genus->wings(2); |
1206 | $genus->update; |
6f1434fd |
1207 | $schema->txn_do($coderef2); # Can have a nested transaction. Only the outer will actualy commit |
181a28f4 |
1208 | return $genus->species; |
1209 | }; |
1210 | |
181a28f4 |
1211 | my $rs; |
1212 | eval { |
70634260 |
1213 | $rs = $schema->txn_do($coderef1); |
181a28f4 |
1214 | }; |
1215 | |
1216 | if ($@) { # Transaction failed |
1217 | die "the sky is falling!" # |
1218 | if ($@ =~ /Rollback failed/); # Rollback failed |
1219 | |
1220 | deal_with_failed_transaction(); |
35d4fe78 |
1221 | } |
87980de7 |
1222 | |
181a28f4 |
1223 | Nested transactions will work as expected. That is, only the outermost |
1224 | transaction will actually issue a commit to the $dbh, and a rollback |
1225 | at any level of any transaction will cause the entire nested |
1226 | transaction to fail. Support for savepoints and for true nested |
40dbc108 |
1227 | transactions (for databases that support them) will hopefully be added |
1228 | in the future. |
ee38fa40 |
1229 | |
d2f3e87b |
1230 | =head1 SQL |
ee38fa40 |
1231 | |
d2f3e87b |
1232 | =head2 Creating Schemas From An Existing Database |
ea6309e2 |
1233 | |
d2f3e87b |
1234 | L<DBIx::Class::Schema::Loader> will connect to a database and create a |
1235 | L<DBIx::Class::Schema> and associated sources by examining the database. |
bade79c4 |
1236 | |
d2f3e87b |
1237 | The recommend way of achieving this is to use the |
1238 | L<make_schema_at|DBIx::Class::Schema::Loader/make_schema_at> method: |
bade79c4 |
1239 | |
6f1434fd |
1240 | perl -MDBIx::Class::Schema::Loader=make_schema_at,dump_to_dir:./lib \ |
1241 | -e 'make_schema_at("My::Schema", { debug => 1 }, [ "dbi:Pg:dbname=foo","postgres" ])' |
362500af |
1242 | |
d2f3e87b |
1243 | This will create a tree of files rooted at C<./lib/My/Schema/> containing |
1244 | source definitions for all the tables found in the C<foo> database. |
362500af |
1245 | |
d2f3e87b |
1246 | =head2 Creating DDL SQL |
362500af |
1247 | |
264f1571 |
1248 | The following functionality requires you to have L<SQL::Translator> |
1249 | (also known as "SQL Fairy") installed. |
362500af |
1250 | |
264f1571 |
1251 | To create a set of database-specific .sql files for the above schema: |
362500af |
1252 | |
264f1571 |
1253 | my $schema = My::Schema->connect($dsn); |
1254 | $schema->create_ddl_dir(['MySQL', 'SQLite', 'PostgreSQL'], |
1255 | '0.1', |
d2f3e87b |
1256 | './dbscriptdir/' |
264f1571 |
1257 | ); |
1258 | |
1259 | By default this will create schema files in the current directory, for |
1260 | MySQL, SQLite and PostgreSQL, using the $VERSION from your Schema.pm. |
1261 | |
1262 | To create a new database using the schema: |
1263 | |
1264 | my $schema = My::Schema->connect($dsn); |
1265 | $schema->deploy({ add_drop_tables => 1}); |
1266 | |
1267 | To import created .sql files using the mysql client: |
1268 | |
1269 | mysql -h "host" -D "database" -u "user" -p < My_Schema_1.0_MySQL.sql |
1270 | |
1271 | To create C<ALTER TABLE> conversion scripts to update a database to a |
1272 | newer version of your schema at a later point, first set a new |
d2f3e87b |
1273 | C<$VERSION> in your Schema file, then: |
264f1571 |
1274 | |
1275 | my $schema = My::Schema->connect($dsn); |
1276 | $schema->create_ddl_dir(['MySQL', 'SQLite', 'PostgreSQL'], |
1277 | '0.2', |
1278 | '/dbscriptdir/', |
1279 | '0.1' |
1280 | ); |
1281 | |
1282 | This will produce new database-specific .sql files for the new version |
1283 | of the schema, plus scripts to convert from version 0.1 to 0.2. This |
1284 | requires that the files for 0.1 as created above are available in the |
1285 | given directory to diff against. |
362500af |
1286 | |
6f1434fd |
1287 | =head2 Select from dual |
16cd5b28 |
1288 | |
1289 | Dummy tables are needed by some databases to allow calling functions |
1290 | or expressions that aren't based on table content, for examples of how |
1291 | this applies to various database types, see: |
1292 | L<http://troels.arvin.dk/db/rdbms/#other-dummy_table>. |
1293 | |
1294 | Note: If you're using Oracles dual table don't B<ever> do anything |
1295 | other than a select, if you CRUD on your dual table you *will* break |
1296 | your database. |
1297 | |
1298 | Make a table class as you would for any other table |
1299 | |
1300 | package MyAppDB::Dual; |
1301 | use strict; |
1302 | use warnings; |
1303 | use base 'DBIx::Class'; |
1304 | __PACKAGE__->load_components("Core"); |
1305 | __PACKAGE__->table("Dual"); |
1306 | __PACKAGE__->add_columns( |
1307 | "dummy", |
1308 | { data_type => "VARCHAR2", is_nullable => 0, size => 1 }, |
1309 | ); |
1310 | |
1311 | Once you've loaded your table class select from it using C<select> |
1312 | and C<as> instead of C<columns> |
1313 | |
1314 | my $rs = $schema->resultset('Dual')->search(undef, |
1315 | { select => [ 'sydate' ], |
1316 | as => [ 'now' ] |
1317 | }, |
1318 | ); |
1319 | |
1320 | All you have to do now is be careful how you access your resultset, the below |
1321 | will not work because there is no column called 'now' in the Dual table class |
1322 | |
1323 | while (my $dual = $rs->next) { |
1324 | print $dual->now."\n"; |
1325 | } |
6f1434fd |
1326 | # Can't locate object method "now" via package "MyAppDB::Dual" at headshot.pl line 23. |
16cd5b28 |
1327 | |
1328 | You could of course use 'dummy' in C<as> instead of 'now', or C<add_columns> to |
1329 | your Dual class for whatever you wanted to select from dual, but that's just |
1330 | silly, instead use C<get_column> |
1331 | |
1332 | while (my $dual = $rs->next) { |
1333 | print $dual->get_column('now')."\n"; |
1334 | } |
1335 | |
1336 | Or use C<cursor> |
1337 | |
1338 | my $cursor = $rs->cursor; |
1339 | while (my @vals = $cursor->next) { |
1340 | print $vals[0]."\n"; |
1341 | } |
336256bc |
1342 | |
1343 | In case you're going to use this "trick" together with L<DBIx::Class::Schema/deploy> or |
1344 | L<DBIx::Class::Schema/create_ddl_dir> a table called "dual" will be created in your |
1345 | current schema. This would overlap "sys.dual" and you could not fetch "sysdate" or |
1346 | "sequence.nextval" anymore from dual. To avoid this problem, just tell |
1347 | L<SQL::Translator> to not create table dual: |
1348 | |
1349 | my $sqlt_args = { |
1350 | add_drop_table => 1, |
1351 | parser_args => { sources => [ grep $_ ne 'Dual', schema->sources ] }, |
1352 | }; |
1353 | $schema->create_ddl_dir( [qw/Oracle/], undef, './sql', undef, $sqlt_args ); |
16cd5b28 |
1354 | |
1355 | Or use L<DBIx::Class::ResultClass::HashRefInflator> |
1356 | |
1357 | $rs->result_class('DBIx::Class::ResultClass::HashRefInflator'); |
1358 | while ( my $dual = $rs->next ) { |
1359 | print $dual->{now}."\n"; |
1360 | } |
1361 | |
1362 | Here are some example C<select> conditions to illustrate the different syntax |
1363 | you could use for doing stuff like |
1364 | C<oracles.heavily(nested(functions_can('take', 'lots'), OF), 'args')> |
1365 | |
1366 | # get a sequence value |
1367 | select => [ 'A_SEQ.nextval' ], |
1368 | |
1369 | # get create table sql |
1370 | select => [ { 'dbms_metadata.get_ddl' => [ "'TABLE'", "'ARTIST'" ]} ], |
1371 | |
1372 | # get a random num between 0 and 100 |
1373 | select => [ { "trunc" => [ { "dbms_random.value" => [0,100] } ]} ], |
1374 | |
1375 | # what year is it? |
1376 | select => [ { 'extract' => [ \'year from sysdate' ] } ], |
1377 | |
1378 | # do some math |
1379 | select => [ {'round' => [{'cos' => [ \'180 * 3.14159265359/180' ]}]}], |
1380 | |
1381 | # which day of the week were you born on? |
6f1434fd |
1382 | select => [{'to_char' => [{'to_date' => [ "'25-DEC-1980'", "'dd-mon-yyyy'" ]}, "'day'"]}], |
16cd5b28 |
1383 | |
1384 | # select 16 rows from dual |
1385 | select => [ "'hello'" ], |
1386 | as => [ 'world' ], |
1387 | group_by => [ 'cube( 1, 2, 3, 4 )' ], |
1388 | |
1389 | |
1390 | |
d2f3e87b |
1391 | =head2 Adding Indexes And Functions To Your SQL |
362500af |
1392 | |
d2f3e87b |
1393 | Often you will want indexes on columns on your table to speed up searching. To |
1394 | do this, create a method called C<sqlt_deploy_hook> in the relevant source |
2d7d8459 |
1395 | class (refer to the advanced |
1396 | L<callback system|DBIx::Class::ResultSource/sqlt_deploy_callback> if you wish |
1397 | to share a hook between multiple sources): |
b0a20454 |
1398 | |
23471103 |
1399 | package My::Schema::Result::Artist; |
b0a20454 |
1400 | |
d2f3e87b |
1401 | __PACKAGE__->table('artist'); |
1402 | __PACKAGE__->add_columns(id => { ... }, name => { ... }) |
b0a20454 |
1403 | |
d2f3e87b |
1404 | sub sqlt_deploy_hook { |
1405 | my ($self, $sqlt_table) = @_; |
1406 | |
1407 | $sqlt_table->add_index(name => 'idx_name', fields => ['name']); |
1408 | } |
1409 | |
1410 | 1; |
1411 | |
1412 | Sometimes you might want to change the index depending on the type of the |
1413 | database for which SQL is being generated: |
1414 | |
1415 | my ($db_type = $sqlt_table->schema->translator->producer_type) |
1416 | =~ s/^SQL::Translator::Producer:://; |
1417 | |
1418 | You can also add hooks to the schema level to stop certain tables being |
1419 | created: |
1420 | |
1421 | package My::Schema; |
1422 | |
1423 | ... |
1424 | |
1425 | sub sqlt_deploy_hook { |
1426 | my ($self, $sqlt_schema) = @_; |
1427 | |
1428 | $sqlt_schema->drop_table('table_name'); |
1429 | } |
1430 | |
2d7d8459 |
1431 | You could also add views, procedures or triggers to the output using |
1432 | L<SQL::Translator::Schema/add_view>, |
1433 | L<SQL::Translator::Schema/add_procedure> or |
1434 | L<SQL::Translator::Schema/add_trigger>. |
1435 | |
b0a20454 |
1436 | |
362500af |
1437 | =head2 Schema versioning |
1438 | |
1439 | The following example shows simplistically how you might use DBIx::Class to |
1440 | deploy versioned schemas to your customers. The basic process is as follows: |
1441 | |
da4779ad |
1442 | =over 4 |
1443 | |
1444 | =item 1. |
1445 | |
1446 | Create a DBIx::Class schema |
1447 | |
1448 | =item 2. |
1449 | |
1450 | Save the schema |
1451 | |
1452 | =item 3. |
1453 | |
1454 | Deploy to customers |
1455 | |
1456 | =item 4. |
1457 | |
1458 | Modify schema to change functionality |
1459 | |
1460 | =item 5. |
1461 | |
1462 | Deploy update to customers |
1463 | |
1464 | =back |
362500af |
1465 | |
d2f3e87b |
1466 | B<Create a DBIx::Class schema> |
362500af |
1467 | |
1468 | This can either be done manually, or generated from an existing database as |
d2f3e87b |
1469 | described under L</Creating Schemas From An Existing Database> |
362500af |
1470 | |
d2f3e87b |
1471 | B<Save the schema> |
362500af |
1472 | |
d2f3e87b |
1473 | Call L<DBIx::Class::Schema/create_ddl_dir> as above under L</Creating DDL SQL>. |
362500af |
1474 | |
d2f3e87b |
1475 | B<Deploy to customers> |
362500af |
1476 | |
1477 | There are several ways you could deploy your schema. These are probably |
1478 | beyond the scope of this recipe, but might include: |
1479 | |
da4779ad |
1480 | =over 4 |
1481 | |
1482 | =item 1. |
1483 | |
1484 | Require customer to apply manually using their RDBMS. |
1485 | |
1486 | =item 2. |
1487 | |
1488 | Package along with your app, making database dump/schema update/tests |
362500af |
1489 | all part of your install. |
1490 | |
da4779ad |
1491 | =back |
1492 | |
d2f3e87b |
1493 | B<Modify the schema to change functionality> |
362500af |
1494 | |
264f1571 |
1495 | As your application evolves, it may be necessary to modify your schema |
1496 | to change functionality. Once the changes are made to your schema in |
1497 | DBIx::Class, export the modified schema and the conversion scripts as |
d2f3e87b |
1498 | in L</Creating DDL SQL>. |
362500af |
1499 | |
d2f3e87b |
1500 | B<Deploy update to customers> |
362500af |
1501 | |
264f1571 |
1502 | Add the L<DBIx::Class::Schema::Versioned> schema component to your |
1503 | Schema class. This will add a new table to your database called |
ecea7937 |
1504 | C<dbix_class_schema_vesion> which will keep track of which version is installed |
264f1571 |
1505 | and warn if the user trys to run a newer schema version than the |
1506 | database thinks it has. |
1507 | |
1508 | Alternatively, you can send the conversion sql scripts to your |
1509 | customers as above. |
362500af |
1510 | |
d2f3e87b |
1511 | =head2 Setting quoting for the generated SQL. |
1512 | |
1513 | If the database contains column names with spaces and/or reserved words, they |
1514 | need to be quoted in the SQL queries. This is done using: |
1515 | |
1516 | __PACKAGE__->storage->sql_maker->quote_char([ qw/[ ]/] ); |
1517 | __PACKAGE__->storage->sql_maker->name_sep('.'); |
1518 | |
1519 | The first sets the quote characters. Either a pair of matching |
1520 | brackets, or a C<"> or C<'>: |
1521 | |
1522 | __PACKAGE__->storage->sql_maker->quote_char('"'); |
1523 | |
1524 | Check the documentation of your database for the correct quote |
1525 | characters to use. C<name_sep> needs to be set to allow the SQL |
1526 | generator to put the quotes the correct place. |
1527 | |
1528 | In most cases you should set these as part of the arguments passed to |
d68b0c69 |
1529 | L<DBIx::Class::Schema/connect>: |
d2f3e87b |
1530 | |
1531 | my $schema = My::Schema->connect( |
1532 | 'dbi:mysql:my_db', |
1533 | 'db_user', |
1534 | 'db_password', |
1535 | { |
1536 | quote_char => '"', |
1537 | name_sep => '.' |
1538 | } |
1539 | ) |
1540 | |
7be93b07 |
1541 | =head2 Setting limit dialect for SQL::Abstract::Limit |
1542 | |
324572ca |
1543 | In some cases, SQL::Abstract::Limit cannot determine the dialect of |
1544 | the remote SQL server by looking at the database handle. This is a |
1545 | common problem when using the DBD::JDBC, since the DBD-driver only |
1546 | know that in has a Java-driver available, not which JDBC driver the |
1547 | Java component has loaded. This specifically sets the limit_dialect |
1548 | to Microsoft SQL-server (See more names in SQL::Abstract::Limit |
1549 | -documentation. |
7be93b07 |
1550 | |
1551 | __PACKAGE__->storage->sql_maker->limit_dialect('mssql'); |
1552 | |
324572ca |
1553 | The JDBC bridge is one way of getting access to a MSSQL server from a platform |
7be93b07 |
1554 | that Microsoft doesn't deliver native client libraries for. (e.g. Linux) |
1555 | |
d2f3e87b |
1556 | The limit dialect can also be set at connect time by specifying a |
1557 | C<limit_dialect> key in the final hash as shown above. |
2437a1e3 |
1558 | |
05697a49 |
1559 | =head2 Working with PostgreSQL array types |
1560 | |
20ea616f |
1561 | You can also assign values to PostgreSQL array columns by passing array |
1562 | references in the C<\%columns> (C<\%vals>) hashref of the |
1563 | L<DBIx::Class::ResultSet/create> and L<DBIx::Class::Row/update> family of |
1564 | methods: |
05697a49 |
1565 | |
1566 | $resultset->create({ |
1567 | numbers => [1, 2, 3] |
1568 | }); |
1569 | |
1570 | $row->update( |
1571 | { |
1572 | numbers => [1, 2, 3] |
1573 | }, |
1574 | { |
1575 | day => '2008-11-24' |
1576 | } |
1577 | ); |
1578 | |
1579 | In conditions (eg. C<\%cond> in the L<DBIx::Class::ResultSet/search> family of |
1580 | methods) you cannot directly use array references (since this is interpreted as |
1581 | a list of values to be C<OR>ed), but you can use the following syntax to force |
1582 | passing them as bind values: |
1583 | |
1584 | $resultset->search( |
1585 | { |
31eb3263 |
1586 | numbers => \[ '= ?', [numbers => [1, 2, 3]] ] |
05697a49 |
1587 | } |
1588 | ); |
1589 | |
1590 | See L<SQL::Abstract/array_datatypes> and L<SQL::Abstract/Literal SQL with |
31eb3263 |
1591 | placeholders and bind values (subqueries)> for more explanation. Note that |
1592 | L<DBIx::Class> sets L<SQL::Abstract/bindtype> to C<columns>, so you must pass |
1593 | the bind values (the C<[1, 2, 3]> arrayref in the above example) wrapped in |
1594 | arrayrefs together with the column name, like this: C<< [column_name => value] |
1595 | >>. |
05697a49 |
1596 | |
d2f3e87b |
1597 | =head1 BOOTSTRAPPING/MIGRATING |
2437a1e3 |
1598 | |
d2f3e87b |
1599 | =head2 Easy migration from class-based to schema-based setup |
2437a1e3 |
1600 | |
d2f3e87b |
1601 | You want to start using the schema-based approach to L<DBIx::Class> |
1602 | (see L<SchemaIntro.pod>), but have an established class-based setup with lots |
1603 | of existing classes that you don't want to move by hand. Try this nifty script |
1604 | instead: |
1605 | |
1606 | use MyDB; |
1607 | use SQL::Translator; |
1608 | |
1609 | my $schema = MyDB->schema_instance; |
2437a1e3 |
1610 | |
d2f3e87b |
1611 | my $translator = SQL::Translator->new( |
1612 | debug => $debug || 0, |
1613 | trace => $trace || 0, |
1614 | no_comments => $no_comments || 0, |
1615 | show_warnings => $show_warnings || 0, |
1616 | add_drop_table => $add_drop_table || 0, |
1617 | validate => $validate || 0, |
1618 | parser_args => { |
1619 | 'DBIx::Schema' => $schema, |
1620 | }, |
1621 | producer_args => { |
1622 | 'prefix' => 'My::Schema', |
1623 | }, |
1624 | ); |
1625 | |
1626 | $translator->parser('SQL::Translator::Parser::DBIx::Class'); |
1627 | $translator->producer('SQL::Translator::Producer::DBIx::Class::File'); |
1628 | |
1629 | my $output = $translator->translate(@args) or die |
1630 | "Error: " . $translator->error; |
1631 | |
1632 | print $output; |
2437a1e3 |
1633 | |
d2f3e87b |
1634 | You could use L<Module::Find> to search for all subclasses in the MyDB::* |
1635 | namespace, which is currently left as an exercise for the reader. |
2437a1e3 |
1636 | |
d2f3e87b |
1637 | =head1 OVERLOADING METHODS |
086b93a2 |
1638 | |
ab872312 |
1639 | L<DBIx::Class> uses the L<Class::C3> package, which provides for redispatch of |
1640 | method calls, useful for things like default values and triggers. You have to |
1641 | use calls to C<next::method> to overload methods. More information on using |
1642 | L<Class::C3> with L<DBIx::Class> can be found in |
086b93a2 |
1643 | L<DBIx::Class::Manual::Component>. |
1644 | |
d2f3e87b |
1645 | =head2 Setting default values for a row |
1646 | |
1647 | It's as simple as overriding the C<new> method. Note the use of |
1648 | C<next::method>. |
1649 | |
1650 | sub new { |
1651 | my ( $class, $attrs ) = @_; |
1652 | |
1653 | $attrs->{foo} = 'bar' unless defined $attrs->{foo}; |
1654 | |
1655 | my $new = $class->next::method($attrs); |
1656 | |
1657 | return $new; |
1658 | } |
1659 | |
1660 | For more information about C<next::method>, look in the L<Class::C3> |
1661 | documentation. See also L<DBIx::Class::Manual::Component> for more |
1662 | ways to write your own base classes to do this. |
1663 | |
1664 | People looking for ways to do "triggers" with DBIx::Class are probably |
1665 | just looking for this. |
1666 | |
1667 | =head2 Changing one field whenever another changes |
086b93a2 |
1668 | |
1669 | For example, say that you have three columns, C<id>, C<number>, and |
1670 | C<squared>. You would like to make changes to C<number> and have |
1671 | C<squared> be automagically set to the value of C<number> squared. |
1672 | You can accomplish this by overriding C<store_column>: |
1673 | |
1674 | sub store_column { |
1675 | my ( $self, $name, $value ) = @_; |
1676 | if ($name eq 'number') { |
1677 | $self->squared($value * $value); |
1678 | } |
1679 | $self->next::method($name, $value); |
1680 | } |
1681 | |
1682 | Note that the hard work is done by the call to C<next::method>, which |
324572ca |
1683 | redispatches your call to store_column in the superclass(es). |
086b93a2 |
1684 | |
d2f3e87b |
1685 | =head2 Automatically creating related objects |
086b93a2 |
1686 | |
324572ca |
1687 | You might have a class C<Artist> which has many C<CD>s. Further, if you |
086b93a2 |
1688 | want to create a C<CD> object every time you insert an C<Artist> object. |
ccbebdbc |
1689 | You can accomplish this by overriding C<insert> on your objects: |
086b93a2 |
1690 | |
1691 | sub insert { |
ccbebdbc |
1692 | my ( $self, @args ) = @_; |
1693 | $self->next::method(@args); |
086b93a2 |
1694 | $self->cds->new({})->fill_from_artist($self)->insert; |
1695 | return $self; |
1696 | } |
1697 | |
1698 | where C<fill_from_artist> is a method you specify in C<CD> which sets |
1699 | values in C<CD> based on the data in the C<Artist> object you pass in. |
1700 | |
d2f3e87b |
1701 | =head2 Wrapping/overloading a column accessor |
1702 | |
1703 | B<Problem:> |
1704 | |
1705 | Say you have a table "Camera" and want to associate a description |
1706 | with each camera. For most cameras, you'll be able to generate the description from |
1707 | the other columns. However, in a few special cases you may want to associate a |
1708 | custom description with a camera. |
1709 | |
1710 | B<Solution:> |
1711 | |
1712 | In your database schema, define a description field in the "Camera" table that |
1713 | can contain text and null values. |
1714 | |
1715 | In DBIC, we'll overload the column accessor to provide a sane default if no |
1716 | custom description is defined. The accessor will either return or generate the |
1717 | description, depending on whether the field is null or not. |
1718 | |
1719 | First, in your "Camera" schema class, define the description field as follows: |
1720 | |
1721 | __PACKAGE__->add_columns(description => { accessor => '_description' }); |
1722 | |
1723 | Next, we'll define the accessor-wrapper subroutine: |
1724 | |
1725 | sub description { |
1726 | my $self = shift; |
1727 | |
1728 | # If there is an update to the column, we'll let the original accessor |
1729 | # deal with it. |
1730 | return $self->_description(@_) if @_; |
1731 | |
1732 | # Fetch the column value. |
1733 | my $description = $self->_description; |
1734 | |
1735 | # If there's something in the description field, then just return that. |
1736 | return $description if defined $description && length $descripton; |
1737 | |
1738 | # Otherwise, generate a description. |
1739 | return $self->generate_description; |
1740 | } |
1741 | |
1742 | =head1 DEBUGGING AND PROFILING |
1743 | |
1744 | =head2 DBIx::Class objects with Data::Dumper |
1def3451 |
1745 | |
1746 | L<Data::Dumper> can be a very useful tool for debugging, but sometimes it can |
1747 | be hard to find the pertinent data in all the data it can generate. |
1748 | Specifically, if one naively tries to use it like so, |
1749 | |
1750 | use Data::Dumper; |
1751 | |
1752 | my $cd = $schema->resultset('CD')->find(1); |
1753 | print Dumper($cd); |
1754 | |
1755 | several pages worth of data from the CD object's schema and result source will |
1756 | be dumped to the screen. Since usually one is only interested in a few column |
1757 | values of the object, this is not very helpful. |
1758 | |
1759 | Luckily, it is possible to modify the data before L<Data::Dumper> outputs |
1760 | it. Simply define a hook that L<Data::Dumper> will call on the object before |
1761 | dumping it. For example, |
1762 | |
1763 | package My::DB::CD; |
1764 | |
1765 | sub _dumper_hook { |
99fb1058 |
1766 | $_[0] = bless { |
1767 | %{ $_[0] }, |
1def3451 |
1768 | result_source => undef, |
99fb1058 |
1769 | }, ref($_[0]); |
1def3451 |
1770 | } |
1771 | |
1772 | [...] |
1773 | |
1774 | use Data::Dumper; |
1775 | |
22139027 |
1776 | local $Data::Dumper::Freezer = '_dumper_hook'; |
1def3451 |
1777 | |
1778 | my $cd = $schema->resultset('CD')->find(1); |
1779 | print Dumper($cd); |
1780 | # dumps $cd without its ResultSource |
1781 | |
1782 | If the structure of your schema is such that there is a common base class for |
1783 | all your table classes, simply put a method similar to C<_dumper_hook> in the |
1784 | base class and set C<$Data::Dumper::Freezer> to its name and L<Data::Dumper> |
1785 | will automagically clean up your data before printing it. See |
1786 | L<Data::Dumper/EXAMPLES> for more information. |
1787 | |
4c248161 |
1788 | =head2 Profiling |
1789 | |
85f78622 |
1790 | When you enable L<DBIx::Class::Storage>'s debugging it prints the SQL |
4c248161 |
1791 | executed as well as notifications of query completion and transaction |
1792 | begin/commit. If you'd like to profile the SQL you can subclass the |
1793 | L<DBIx::Class::Storage::Statistics> class and write your own profiling |
1794 | mechanism: |
1795 | |
1796 | package My::Profiler; |
1797 | use strict; |
1798 | |
1799 | use base 'DBIx::Class::Storage::Statistics'; |
1800 | |
1801 | use Time::HiRes qw(time); |
1802 | |
1803 | my $start; |
1804 | |
1805 | sub query_start { |
1806 | my $self = shift(); |
1807 | my $sql = shift(); |
1808 | my $params = @_; |
1809 | |
70f39278 |
1810 | $self->print("Executing $sql: ".join(', ', @params)."\n"); |
4c248161 |
1811 | $start = time(); |
1812 | } |
1813 | |
1814 | sub query_end { |
1815 | my $self = shift(); |
1816 | my $sql = shift(); |
1817 | my @params = @_; |
1818 | |
70f39278 |
1819 | my $elapsed = sprintf("%0.4f", time() - $start); |
1820 | $self->print("Execution took $elapsed seconds.\n"); |
4c248161 |
1821 | $start = undef; |
1822 | } |
1823 | |
1824 | 1; |
1825 | |
1826 | You can then install that class as the debugging object: |
1827 | |
70f39278 |
1828 | __PACKAGE__->storage->debugobj(new My::Profiler()); |
1829 | __PACKAGE__->storage->debug(1); |
4c248161 |
1830 | |
1831 | A more complicated example might involve storing each execution of SQL in an |
1832 | array: |
1833 | |
1834 | sub query_end { |
1835 | my $self = shift(); |
1836 | my $sql = shift(); |
1837 | my @params = @_; |
1838 | |
1839 | my $elapsed = time() - $start; |
1840 | push(@{ $calls{$sql} }, { |
1841 | params => \@params, |
1842 | elapsed => $elapsed |
1843 | }); |
1844 | } |
1845 | |
1846 | You could then create average, high and low execution times for an SQL |
1847 | statement and dig down to see if certain parameters cause aberrant behavior. |
70f39278 |
1848 | You might want to check out L<DBIx::Class::QueryLog> as well. |
4c248161 |
1849 | |
bc96f260 |
1850 | =head1 STARTUP SPEED |
1851 | |
1852 | L<DBIx::Class|DBIx::Class> programs can have a significant startup delay |
1853 | as the ORM loads all the relevant classes. This section examines |
1854 | techniques for reducing the startup delay. |
1855 | |
1856 | These tips are are listed in order of decreasing effectiveness - so the |
1857 | first tip, if applicable, should have the greatest effect on your |
1858 | application. |
1859 | |
1860 | =head2 Statically Define Your Schema |
1861 | |
1862 | If you are using |
1863 | L<DBIx::Class::Schema::Loader|DBIx::Class::Schema::Loader> to build the |
1864 | classes dynamically based on the database schema then there will be a |
1865 | significant startup delay. |
1866 | |
1867 | For production use a statically defined schema (which can be generated |
1868 | using L<DBIx::Class::Schema::Loader|DBIx::Class::Schema::Loader> to dump |
1869 | the database schema once - see |
1870 | L<make_schema_at|DBIx::Class::Schema::Loader/make_schema_at> and |
1871 | L<dump_directory|DBIx::Class::Schema::Loader/dump_directory> for more |
1872 | details on creating static schemas from a database). |
1873 | |
1874 | =head2 Move Common Startup into a Base Class |
1875 | |
1876 | Typically L<DBIx::Class> result classes start off with |
1877 | |
1878 | use base qw/DBIx::Class/; |
1879 | __PACKAGE__->load_components(qw/InflateColumn::DateTime Core/); |
1880 | |
1881 | If this preamble is moved into a common base class:- |
1882 | |
1883 | package MyDBICbase; |
1884 | |
1885 | use base qw/DBIx::Class/; |
1886 | __PACKAGE__->load_components(qw/InflateColumn::DateTime Core/); |
1887 | 1; |
1888 | |
1889 | and each result class then uses this as a base:- |
1890 | |
1891 | use base qw/MyDBICbase/; |
1892 | |
1893 | then the load_components is only performed once, which can result in a |
1894 | considerable startup speedup for schemas with many classes. |
1895 | |
1896 | =head2 Explicitly List Schema Result Classes |
1897 | |
1898 | The schema class will normally contain |
1899 | |
1900 | __PACKAGE__->load_classes(); |
1901 | |
1902 | to load the result classes. This will use L<Module::Find|Module::Find> |
1903 | to find and load the appropriate modules. Explicitly defining the |
1904 | classes you wish to load will remove the overhead of |
1905 | L<Module::Find|Module::Find> and the related directory operations:- |
1906 | |
1907 | __PACKAGE__->load_classes(qw/ CD Artist Track /); |
1908 | |
1909 | If you are instead using the L<load_namespaces|DBIx::Class::Schema/load_namespaces> |
1910 | syntax to load the appropriate classes there is not a direct alternative |
1911 | avoiding L<Module::Find|Module::Find>. |
7aaec96c |
1912 | |
f4db5947 |
1913 | =head1 MEMORY USAGE |
1914 | |
1915 | =head2 Cached statements |
1916 | |
1917 | L<DBIx::Class> normally caches all statements with L<< prepare_cached()|DBI/prepare_cached >>. |
1918 | This is normally a good idea, but if too many statements are cached, the database may use too much |
1919 | memory and may eventually run out and fail entirely. If you suspect this may be the case, you may want |
1920 | to examine DBI's L<< CachedKids|DBI/CachedKidsCachedKids_(hash_ref) >> hash: |
1921 | |
1922 | # print all currently cached prepared statements |
1923 | print for keys %{$schema->storage->dbh->{CachedKids}}; |
1924 | # get a count of currently cached prepared statements |
1925 | my $count = scalar keys %{$schema->storage->dbh->{CachedKids}}; |
1926 | |
1927 | If it's appropriate, you can simply clear these statements, automatically deallocating them in the |
1928 | database: |
1929 | |
1930 | my $kids = $schema->storage->dbh->{CachedKids}; |
1931 | delete @{$kids}{keys %$kids} if scalar keys %$kids > 100; |
1932 | |
1933 | But what you probably want is to expire unused statements and not those that are used frequently. |
1934 | You can accomplish this with L<Tie::Cache> or L<Tie::Cache::LRU>: |
1935 | |
1936 | use Tie::Cache; |
1937 | use DB::Main; |
1938 | my $schema = DB::Main->connect($dbi_dsn, $user, $pass, { |
1939 | on_connect_do => sub { tie %{shift->_dbh->{CachedKids}}, 'Tie::Cache', 100 }, |
1940 | }); |
1941 | |
40dbc108 |
1942 | =cut |