Class::DBI::Loader::mysql::Grok - Build Quality Table Relationships Automatically


Class-DBI-Loader-mysql-Grok documentation  | view source Contained in the Class-DBI-Loader-mysql-Grok distribution.

Index


NAME

Top

Class::DBI::Loader::mysql::Grok - Build Quality Table Relationships Automatically

SYNOPSIS

Top

  use Class::DBI::Loader; # optional
  use Class::DBI::Loader::mysql::Grok;

  my $loader = Class::DBI::Loader->new(
    ...
    namespace     => "Music",
    relationships => 1,
  );

  my $class  = $loader->find_class('artist'); # $class => Music::Artist
  my $artist = $class->retrieve(1);

  for my $cd ($artist->cds) {
  	print $cd->artist->name,"\n";
	print $cd->reldate->ymd,"\n"; # a Time::Piece object
  }

  # etc ...

DESCRIPTION

Top

If you name your tables and columns using some common sense rules, there's no need for you to do any work to have proper db abstraction. The following examples mostly follow the Class::DBI perldoc. To see where they differ (immaterially), see the test script and the accompanying SQL.

The kinds of relationships which are created include:

In the example above, the cd table contains a column which matches the name of another table: artist. In this case, Music::Cd objects have a has_a relationship with Music::Artist. As a result, you can call $cd->artist->name, etc.

Similar to the has_a example above, the fact that the cd table contains a column which matches the name of another table means that Music::Artist objects have a has_many relationship with Music::CD. As a result, you can call $artist->cds->next->title, etc.

When we're working with a mapping table like Music::StyleRef in the Class::DBI perldoc, which maps a many-to-many relationship, the mapping table name must =~ /_ref$/i, and the columns in that table must be named after the tables to which they refer.

The liner_notes table's primary key is named 'cd'. Since that's so, and the table name (liner_notes) !~ /_ref$/i: Music::Cd->might_have(liner_notes_notes => Music::LinerNotes => 'notes');

While not a multi-table relationship, Time::Piece support is included for date, time, datetime, and timestamp types.

EXPORT

None by default, but it does redefine the _relationships routine in Class::DBI::Loader::mysql.

SEE ALSO

Top

Class::DBI Class::DBI::Loader, Class::DBI::Loader::mysql, Time::Piece

AUTHOR

Top

James Tolley, <james@bitperfect.com>

COPYRIGHT AND LICENSE

Top


Class-DBI-Loader-mysql-Grok documentation  | view source Contained in the Class-DBI-Loader-mysql-Grok distribution.