From Redis to Postgres - Part 1

[gruntmaster-data.git] / lib / Gruntmaster / Data / Result / ContestProblem.pm

diff --git a/lib/Gruntmaster/Data/Result/ContestProblem.pm b/lib/Gruntmaster/Data/Result/ContestProblem.pm
new file mode 100644 (file)
index 0000000..a1fe4b4
--- /dev/null
+++ b/lib/Gruntmaster/Data/Result/ContestProblem.pm
@@ -0,0 +1,99 @@
+use utf8;
+package Gruntmaster::Data::Result::ContestProblem;
+
+# Created by DBIx::Class::Schema::Loader
+# DO NOT MODIFY THE FIRST PART OF THIS FILE
+
+=head1 NAME
+
+Gruntmaster::Data::Result::ContestProblem
+
+=cut
+
+use strict;
+use warnings;
+
+use base 'DBIx::Class::Core';
+
+=head1 TABLE: C<contest_problems>
+
+=cut
+
+__PACKAGE__->table("contest_problems");
+
+=head1 ACCESSORS
+
+=head2 contest
+
+  data_type: 'text'
+  is_foreign_key: 1
+  is_nullable: 0
+
+=head2 problem
+
+  data_type: 'text'
+  is_foreign_key: 1
+  is_nullable: 0
+
+=cut
+
+__PACKAGE__->add_columns(
+  "contest",
+  { data_type => "text", is_foreign_key => 1, is_nullable => 0 },
+  "problem",
+  { data_type => "text", is_foreign_key => 1, is_nullable => 0 },
+);
+
+=head1 PRIMARY KEY
+
+=over 4
+
+=item * L</contest>
+
+=item * L</problem>
+
+=back
+
+=cut
+
+__PACKAGE__->set_primary_key("contest", "problem");
+
+=head1 RELATIONS
+
+=head2 contest
+
+Type: belongs_to
+
+Related object: L<Gruntmaster::Data::Result::Contest>
+
+=cut
+
+__PACKAGE__->belongs_to(
+  "contest",
+  "Gruntmaster::Data::Result::Contest",
+  { id => "contest" },
+  { is_deferrable => 0, on_delete => "NO ACTION", on_update => "NO ACTION" },
+);
+
+=head2 problem
+
+Type: belongs_to
+
+Related object: L<Gruntmaster::Data::Result::Problem>
+
+=cut
+
+__PACKAGE__->belongs_to(
+  "problem",
+  "Gruntmaster::Data::Result::Problem",
+  { id => "problem" },
+  { is_deferrable => 0, on_delete => "NO ACTION", on_update => "NO ACTION" },
+);
+
+
+# Created by DBIx::Class::Schema::Loader v0.07039 @ 2014-03-06 12:41:16
+# DO NOT MODIFY THIS OR ANYTHING ABOVE! md5sum:2vVP0Z6QcLz8DiobdOceyQ
+
+
+# You can replace this text with custom code or comments, and it will be preserved on regeneration
+1;