Parents (Total: 5)

The searched file hash is included in 5 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	6BB3CC96EEB40829905717A46D06747B
PackageArch	noarch
PackageDescription	This is a Catalyst Model for DBIx::Class::Schema-based Models. See the documentation for Catalyst::Helper::Model::DBIC::Schema for information on generating these Models via Helper scripts. When your Catalyst app starts up, a thin Model layer is created as an interface to your DBIC Schema. It should be clearly noted that the model object returned by '$c->model('FilmDB')' is NOT itself a DBIC schema or resultset object, but merely a wrapper proving methods to access the underlying schema. In addition to this model class, a shortcut class is generated for each source in the schema, allowing easy and direct access to a resultset of the corresponding type. These generated classes are even thinner than the model class, providing no public methods but simply hooking into Catalyst's model() accessor via the ACCEPT_CONTEXT mechanism. The complete contents of each generated class is roughly equivalent to the following: package MyApp::Model::FilmDB::Actor sub ACCEPT_CONTEXT { my ($self, $c) = @_; $c->model('FilmDB')->resultset('Actor'); } In short, there are three techniques available for obtaining a DBIC resultset object: my $rs = $c->model('FilmDB')->schema->resultset('Actor'); my $rs = $c->model('FilmDB')->resultset('Actor'); my $rs = $c->model('FilmDB::Actor'); In order to add methods to a DBIC resultset, you cannot simply add them to the source (row, table) definition class; you must define a separate custom resultset class. This is just a matter of making a 'lib/MyApp/Schema/ResultSet/Actor.pm' class that inherits from DBIx::Class::ResultSet, if you are using DBIx::Class::Schema/load_namespaces, the default for helper script generated schemas. See DBIx::Class::Manual::Cookbook/"Predefined searches" for information on definining your own DBIx::Class::ResultSet classes for use with DBIx::Class::Schema/load_classes, the old default.
PackageName	perl-Catalyst-Model-DBIC-Schema
PackageRelease	2.43
PackageVersion	0.65
SHA-1	61F184A739CB2E8F432E4023E9D7D1576213E465
SHA-256	03A13A184192B428DA132D99C0775DC9E79D34DBF399A3B65620700366DEB9E4

Key	Value
MD5	7599F3EB5F38DECA26CA04EDB54BE93B
PackageArch	noarch
PackageDescription	This is a Catalyst Model for DBIx::Class::Schema-based Models. See the documentation for Catalyst::Helper::Model::DBIC::Schema for information on generating these Models via Helper scripts. When your Catalyst app starts up, a thin Model layer is created as an interface to your DBIC Schema. It should be clearly noted that the model object returned by '$c->model('FilmDB')' is NOT itself a DBIC schema or resultset object, but merely a wrapper proving methods to access the underlying schema. In addition to this model class, a shortcut class is generated for each source in the schema, allowing easy and direct access to a resultset of the corresponding type. These generated classes are even thinner than the model class, providing no public methods but simply hooking into Catalyst's model() accessor via the ACCEPT_CONTEXT mechanism. The complete contents of each generated class is roughly equivalent to the following: package MyApp::Model::FilmDB::Actor sub ACCEPT_CONTEXT { my ($self, $c) = @_; $c->model('FilmDB')->resultset('Actor'); } In short, there are three techniques available for obtaining a DBIC resultset object: my $rs = $c->model('FilmDB')->schema->resultset('Actor'); my $rs = $c->model('FilmDB')->resultset('Actor'); my $rs = $c->model('FilmDB::Actor'); In order to add methods to a DBIC resultset, you cannot simply add them to the source (row, table) definition class; you must define a separate custom resultset class. This is just a matter of making a 'lib/MyApp/Schema/ResultSet/Actor.pm' class that inherits from DBIx::Class::ResultSet, if you are using DBIx::Class::Schema/load_namespaces, the default for helper script generated schemas. See DBIx::Class::Manual::Cookbook/"Predefined searches" for information on definining your own DBIx::Class::ResultSet classes for use with DBIx::Class::Schema/load_classes, the old default.
PackageName	perl-Catalyst-Model-DBIC-Schema
PackageRelease	lp151.2.1
PackageVersion	0.65
SHA-1	E9789214D3B91A49E7D36EE9DC1DE11D50816200
SHA-256	A0A07CB119A1199CC60A1B0128F027A8A1F2A85FAEE4FD53F1905074721AD074

Key	Value
MD5	49711F673446EA484D4EF8160D57CCD6
PackageArch	noarch
PackageDescription	This is a Catalyst Model for DBIx::Class::Schema-based Models. See the documentation for Catalyst::Helper::Model::DBIC::Schema for information on generating these Models via Helper scripts. When your Catalyst app starts up, a thin Model layer is created as an interface to your DBIC Schema. It should be clearly noted that the model object returned by '$c->model('FilmDB')' is NOT itself a DBIC schema or resultset object, but merely a wrapper proving methods to access the underlying schema. In addition to this model class, a shortcut class is generated for each source in the schema, allowing easy and direct access to a resultset of the corresponding type. These generated classes are even thinner than the model class, providing no public methods but simply hooking into Catalyst's model() accessor via the ACCEPT_CONTEXT mechanism. The complete contents of each generated class is roughly equivalent to the following: package MyApp::Model::FilmDB::Actor sub ACCEPT_CONTEXT { my ($self, $c) = @_; $c->model('FilmDB')->resultset('Actor'); } In short, there are three techniques available for obtaining a DBIC resultset object: my $rs = $c->model('FilmDB')->schema->resultset('Actor'); my $rs = $c->model('FilmDB')->resultset('Actor'); my $rs = $c->model('FilmDB::Actor'); In order to add methods to a DBIC resultset, you cannot simply add them to the source (row, table) definition class; you must define a separate custom resultset class. This is just a matter of making a 'lib/MyApp/Schema/ResultSet/Actor.pm' class that inherits from DBIx::Class::ResultSet, if you are using DBIx::Class::Schema/load_namespaces, the default for helper script generated schemas. See DBIx::Class::Manual::Cookbook/"Predefined searches" for information on definining your own DBIx::Class::ResultSet classes for use with DBIx::Class::Schema/load_classes, the old default.
PackageName	perl-Catalyst-Model-DBIC-Schema
PackageRelease	lp153.2.1
PackageVersion	0.65
SHA-1	7A25A36A7153A7F9F97EF7E78056494AD718337D
SHA-256	7526844162416C763A89BB71C159D9EF9B122DE5F334942A78DF784B2695BA32

Key	Value
MD5	7A952B3D6B7F08634724AEF42A74563D
PackageArch	noarch
PackageDescription	This is a Catalyst Model for DBIx::Class::Schema-based Models. See the documentation for Catalyst::Helper::Model::DBIC::Schema for information on generating these Models via Helper scripts. When your Catalyst app starts up, a thin Model layer is created as an interface to your DBIC Schema. It should be clearly noted that the model object returned by '$c->model('FilmDB')' is NOT itself a DBIC schema or resultset object, but merely a wrapper proving methods to access the underlying schema. In addition to this model class, a shortcut class is generated for each source in the schema, allowing easy and direct access to a resultset of the corresponding type. These generated classes are even thinner than the model class, providing no public methods but simply hooking into Catalyst's model() accessor via the ACCEPT_CONTEXT mechanism. The complete contents of each generated class is roughly equivalent to the following: package MyApp::Model::FilmDB::Actor sub ACCEPT_CONTEXT { my ($self, $c) = @_; $c->model('FilmDB')->resultset('Actor'); } In short, there are three techniques available for obtaining a DBIC resultset object: my $rs = $c->model('FilmDB')->schema->resultset('Actor'); my $rs = $c->model('FilmDB')->resultset('Actor'); my $rs = $c->model('FilmDB::Actor'); In order to add methods to a DBIC resultset, you cannot simply add them to the source (row, table) definition class; you must define a separate custom resultset class. This is just a matter of making a 'lib/MyApp/Schema/ResultSet/Actor.pm' class that inherits from DBIx::Class::ResultSet, if you are using DBIx::Class::Schema/load_namespaces, the default for helper script generated schemas. See DBIx::Class::Manual::Cookbook/"Predefined searches" for information on definining your own DBIx::Class::ResultSet classes for use with DBIx::Class::Schema/load_classes, the old default.
PackageName	perl-Catalyst-Model-DBIC-Schema
PackageRelease	lp150.2.1
PackageVersion	0.65
SHA-1	FD82337DF54C7926D24418FCCCA0FBF1BE2129BE
SHA-256	34BEE472290AB07CCE1141724615D33D3D3376446C74A903F22812146F5CDA1E

Key	Value
MD5	15472602641879624EDA3B6CEB05DEAF
PackageArch	noarch
PackageDescription	This is a Catalyst Model for DBIx::Class::Schema-based Models. See the documentation for Catalyst::Helper::Model::DBIC::Schema for information on generating these Models via Helper scripts. When your Catalyst app starts up, a thin Model layer is created as an interface to your DBIC Schema. It should be clearly noted that the model object returned by '$c->model('FilmDB')' is NOT itself a DBIC schema or resultset object, but merely a wrapper proving methods to access the underlying schema. In addition to this model class, a shortcut class is generated for each source in the schema, allowing easy and direct access to a resultset of the corresponding type. These generated classes are even thinner than the model class, providing no public methods but simply hooking into Catalyst's model() accessor via the ACCEPT_CONTEXT mechanism. The complete contents of each generated class is roughly equivalent to the following: package MyApp::Model::FilmDB::Actor sub ACCEPT_CONTEXT { my ($self, $c) = @_; $c->model('FilmDB')->resultset('Actor'); } In short, there are three techniques available for obtaining a DBIC resultset object: my $rs = $c->model('FilmDB')->schema->resultset('Actor'); my $rs = $c->model('FilmDB')->resultset('Actor'); my $rs = $c->model('FilmDB::Actor'); In order to add methods to a DBIC resultset, you cannot simply add them to the source (row, table) definition class; you must define a separate custom resultset class. This is just a matter of making a 'lib/MyApp/Schema/ResultSet/Actor.pm' class that inherits from DBIx::Class::ResultSet, if you are using DBIx::Class::Schema/load_namespaces, the default for helper script generated schemas. See DBIx::Class::Manual::Cookbook/"Predefined searches" for information on definining your own DBIx::Class::ResultSet classes for use with DBIx::Class::Schema/load_classes, the old default.
PackageName	perl-Catalyst-Model-DBIC-Schema
PackageRelease	lp152.2.1
PackageVersion	0.65
SHA-1	C888BBDA2362EB3F3DEE8A463FB5C6D5E6C1DF47
SHA-256	BECA041D5377C3018DF712FD52DFA58154FBA3E11D27DADF867D3143C3BFF542