Revision history for DBIx::Class
-0.05990_03
+0.05999_03
- deploy now adds drop statements before creates
- - deploy outputs debugging statements if DBIX_CLASS_STORAGE_DBI_DEBUG is set
+ - deploy outputs debugging statements if DBIX_CLASS_STORAGE_DBI_DEBUG
+ is set
-0.05990_02 2006-03-10 13:31:37
+0.05999_02 2006-03-10 13:31:37
- remove test dep on YAML
- additional speed tweaks for C3
- allow scalarefs passed to order_by to go straight through to SQL
__PACKAGE__->set_primary_key( qw/ albumid artistid / );
+=begin hide
+
You can define relationships for any of your classes. L<DBIx::Class> will
automatically fill in the correct namespace, so if you want to say
"a My::Schema::Album object belongs to a My::Schema::Artist object" you do not
__PACKAGE__->belongs_to('artist' => 'Artist');
+=end hide
+
That's all you need in terms of setup.
=head2 Usage
is( scalar @{ $rs->get_cache }, 0, 'cache is not populated without cache attribute' );
+my @a = $schema->resultset("Artist")->search(
+ { },
+ {
+ join => [ qw/ cds /],
+ prefetch => [qw/ cds /],
+ }
+);
+
+is(scalar @a, 3, 'artist with cds: count parent objects');
+
$rs = $schema->resultset("Artist")->search(
{ 'artistid' => 1 },
{