/usr/share/perl5/Bio/Chado/Schema/Result/Cv/CvtermDbxref.pm is in libbio-chado-schema-perl 0.20000-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 | package Bio::Chado::Schema::Result::Cv::CvtermDbxref;
BEGIN {
$Bio::Chado::Schema::Result::Cv::CvtermDbxref::AUTHORITY = 'cpan:RBUELS';
}
{
$Bio::Chado::Schema::Result::Cv::CvtermDbxref::VERSION = '0.20000';
}
# Created by DBIx::Class::Schema::Loader
# DO NOT MODIFY THE FIRST PART OF THIS FILE
use strict;
use warnings;
use base 'DBIx::Class::Core';
=head1 NAME
Bio::Chado::Schema::Result::Cv::CvtermDbxref
=head1 DESCRIPTION
In addition to the primary
identifier (cvterm.dbxref_id) a cvterm can have zero or more secondary
identifiers/dbxrefs, which may refer to records in external
databases. The exact semantics of cvterm_dbxref are not fixed. For
example: the dbxref could be a pubmed ID that is pertinent to the
cvterm, or it could be an equivalent or similar term in another
ontology. For example, GO cvterms are typically linked to InterPro
IDs, even though the nature of the relationship between them is
largely one of statistical association. The dbxref may be have data
records attached in the same database instance, or it could be a
"hanging" dbxref pointing to some external database. NOTE: If the
desired objective is to link two cvterms together, and the nature of
the relation is known and holds for all instances of the subject
cvterm then consider instead using cvterm_relationship together with a
well-defined relation.
=cut
__PACKAGE__->table("cvterm_dbxref");
=head1 ACCESSORS
=head2 cvterm_dbxref_id
data_type: 'integer'
is_auto_increment: 1
is_nullable: 0
sequence: 'cvterm_dbxref_cvterm_dbxref_id_seq'
=head2 cvterm_id
data_type: 'integer'
is_foreign_key: 1
is_nullable: 0
=head2 dbxref_id
data_type: 'integer'
is_foreign_key: 1
is_nullable: 0
=head2 is_for_definition
data_type: 'integer'
default_value: 0
is_nullable: 0
A
cvterm.definition should be supported by one or more references. If
this column is true, the dbxref is not for a term in an external database -
it is a dbxref for provenance information for the definition.
=cut
__PACKAGE__->add_columns(
"cvterm_dbxref_id",
{
data_type => "integer",
is_auto_increment => 1,
is_nullable => 0,
sequence => "cvterm_dbxref_cvterm_dbxref_id_seq",
},
"cvterm_id",
{ data_type => "integer", is_foreign_key => 1, is_nullable => 0 },
"dbxref_id",
{ data_type => "integer", is_foreign_key => 1, is_nullable => 0 },
"is_for_definition",
{ data_type => "integer", default_value => 0, is_nullable => 0 },
);
__PACKAGE__->set_primary_key("cvterm_dbxref_id");
__PACKAGE__->add_unique_constraint("cvterm_dbxref_c1", ["cvterm_id", "dbxref_id"]);
=head1 RELATIONS
=head2 dbxref
Type: belongs_to
Related object: L<Bio::Chado::Schema::Result::General::Dbxref>
=cut
__PACKAGE__->belongs_to(
"dbxref",
"Bio::Chado::Schema::Result::General::Dbxref",
{ dbxref_id => "dbxref_id" },
{
cascade_copy => 0,
cascade_delete => 0,
is_deferrable => 1,
on_delete => "CASCADE",
on_update => "CASCADE",
},
);
=head2 cvterm
Type: belongs_to
Related object: L<Bio::Chado::Schema::Result::Cv::Cvterm>
=cut
__PACKAGE__->belongs_to(
"cvterm",
"Bio::Chado::Schema::Result::Cv::Cvterm",
{ cvterm_id => "cvterm_id" },
{
cascade_copy => 0,
cascade_delete => 0,
is_deferrable => 1,
on_delete => "CASCADE",
on_update => "CASCADE",
},
);
# Created by DBIx::Class::Schema::Loader v0.07010 @ 2011-03-16 23:09:58
# DO NOT MODIFY THIS OR ANYTHING ABOVE! md5sum:tnzyKdGKsHmaJUobXwNC1g
# You can replace this text with custom content, and it will be preserved on regeneration
1;
|