|
NAMEClass::DBI::Relationship - base class for RelationshipsDESCRIPTIONA Class::DBI class represents a database table. But merely being able to represent single tables isn't really that useful - databases are all about relationships.So, Class::DBI provides a variety of Relationship models to represent common database occurences (HasA, HasMany and MightHave), and provides a way to add others. SUBCLASSINGRelationships should inherit from Class::DBI::Relationship, and provide a variety of methods to represent the relationship. For examples of how these are used see Class::DBI::Relationship::HasA, Class::DBI::Relationship::HasMany and Class::DBI::Relationship::MightHave.remap_argumentssub remap_arguments { my $self = shift; # process @_; return ($class, accessor, $foreign_class, $args) } Subclasses should define a 'remap_arguments' method that takes the arguments with which your relationship method will be called, and transforms them into the structure that the Relationship modules requires. If this method is not provided, then it is assumed that your method will be called with these 3 arguments in this order. This should return a list of 4 items:
triggerssub triggers { return ( before_create => sub { ... }, after_create => sub { ... }, ); } Subclasses may define a 'triggers' method that returns a list of triggers that the relationship needs. This method can be omitted if there are no triggers to be set up. methodssub methods { return ( method1 => sub { ... }, method2 => sub { ... }, ); } Subclasses may define a 'methods' method that returns a list of methods to facilitate the relationship that should be created in the calling Class::DBI class. This method can be omitted if there are no methods to be set up.
Visit the GSP FreeBSD Man Page Interface. |