ahuston-0/hydra
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity
hydra/src/lib/Hydra/Schema/Users.pm

175 lines
2.7 KiB
Perl
Raw Normal View History

Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
use utf8;
* Added authentication.
2008-11-26 19:48:04 +00:00
package Hydra::Schema::Users;
2009-10-23 15:05:16 +00:00
# Created by DBIx::Class::Schema::Loader
# DO NOT MODIFY THE FIRST PART OF THIS FILE
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head1 NAME
Hydra::Schema::Users
=cut
* Added authentication.
2008-11-26 19:48:04 +00:00
use strict;
use warnings;
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
use base 'DBIx::Class::Core';
Merge in the first bits of the API work The catalyst-action-rest branch from shlevy/hydra was an exploration of using Catalyst::Action::REST to create a JSON API for hydra. This commit merges in the best bits from that experiment, with the goal that further API endpoints can be added incrementally. In addition to migrating more endpoints, there is potential for improvement in what's already been done: * The web interface can be updated to use the same non-GET endpoints as the JSON interface (using x-tunneled-method) instead of having a separate endpoint * The web rendering should use the $c->stash->{resource} data structure where applicable rather than putting the same data in two places in the stash * Which columns to render for each endpoint is a completely debatable question * Hydra::Component::ToJSON should turn has_many relations that have strings as their primary keys into objects instead of arrays Fixes NixOS/hydra#98 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-06-17 12:34:21 -04:00
=head1 COMPONENTS LOADED
=over 4
=item * L<Hydra::Component::ToJSON>
=back
=cut
__PACKAGE__->load_components("+Hydra::Component::ToJSON");
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head1 TABLE: C<Users>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
* Added authentication.
2008-11-26 19:48:04 +00:00
__PACKAGE__->table("Users");
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=head1 ACCESSORS
=head2 username
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 0
=head2 fullname
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 1
=head2 emailaddress
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 0
=head2 password
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 0
=head2 emailonerror
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'integer'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
default_value: 0
is_nullable: 0
=cut
* Added authentication.
2008-11-26 19:48:04 +00:00
__PACKAGE__->add_columns(
"username",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_nullable => 0 },
* Added authentication.
2008-11-26 19:48:04 +00:00
"fullname",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_nullable => 1 },
* Added authentication.
2008-11-26 19:48:04 +00:00
"emailaddress",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_nullable => 0 },
* Added authentication.
2008-11-26 19:48:04 +00:00
"password",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_nullable => 0 },
* email notification of evaluation errors to project owner (if desired)
2009-12-18 12:07:45 +00:00
"emailonerror",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "integer", default_value => 0, is_nullable => 0 },
* Added authentication.
2008-11-26 19:48:04 +00:00
);
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head1 PRIMARY KEY
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=over 4
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=item * L</username>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=back
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
__PACKAGE__->set_primary_key("username");
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head1 RELATIONS
=head2 newsitems
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Type: has_many
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
Related object: L<Hydra::Schema::NewsItems>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
* Cleaned up the foreign key constraints. * Generate SQLite and PostgreSQL schemas from hydra.sql.
2009-10-21 12:25:43 +00:00
__PACKAGE__->has_many(
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
"newsitems",
"Hydra::Schema::NewsItems",
{ "foreign.author" => "self.username" },
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
undef,
* Cleaned up the foreign key constraints. * Generate SQLite and PostgreSQL schemas from hydra.sql.
2009-10-21 12:25:43 +00:00
);
* Added authentication.
2008-11-26 19:48:04 +00:00
added newsitems, added some admin options to clear various caches.
2010-04-27 13:29:08 +00:00
=head2 projectmembers
Type: has_many
Related object: L<Hydra::Schema::ProjectMembers>
=cut
__PACKAGE__->has_many(
"projectmembers",
"Hydra::Schema::ProjectMembers",
{ "foreign.username" => "self.username" },
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
undef,
added newsitems, added some admin options to clear various caches.
2010-04-27 13:29:08 +00:00
);
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
=head2 projects_2s
added newsitems, added some admin options to clear various caches.
2010-04-27 13:29:08 +00:00
Type: has_many
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
Related object: L<Hydra::Schema::Projects>
added newsitems, added some admin options to clear various caches.
2010-04-27 13:29:08 +00:00
=cut
__PACKAGE__->has_many(
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
"projects_2s",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
"Hydra::Schema::Projects",
{ "foreign.owner" => "self.username" },
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
undef,
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
);
=head2 userroles
Type: has_many
Related object: L<Hydra::Schema::UserRoles>
=cut
__PACKAGE__->has_many(
"userroles",
"Hydra::Schema::UserRoles",
{ "foreign.username" => "self.username" },
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
undef,
added newsitems, added some admin options to clear various caches.
2010-04-27 13:29:08 +00:00
);
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
=head2 projects
Type: many_to_many
Composing rels: L</projectmembers> -> project
=cut
__PACKAGE__->many_to_many("projects", "projectmembers", "project");
added newsitems, added some admin options to clear various caches.
2010-04-27 13:29:08 +00:00
Merge in the first bits of the API work The catalyst-action-rest branch from shlevy/hydra was an exploration of using Catalyst::Action::REST to create a JSON API for hydra. This commit merges in the best bits from that experiment, with the goal that further API endpoints can be added incrementally. In addition to migrating more endpoints, there is potential for improvement in what's already been done: * The web interface can be updated to use the same non-GET endpoints as the JSON interface (using x-tunneled-method) instead of having a separate endpoint * The web rendering should use the $c->stash->{resource} data structure where applicable rather than putting the same data in two places in the stash * Which columns to render for each endpoint is a completely debatable question * Hydra::Component::ToJSON should turn has_many relations that have strings as their primary keys into objects instead of arrays Fixes NixOS/hydra#98 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-06-17 12:34:21 -04:00
# Created by DBIx::Class::Schema::Loader v0.07033 @ 2013-06-13 01:54:50
# DO NOT MODIFY THIS OR ANYTHING ABOVE! md5sum:hy3MKvFxfL+1bTc7Hcb1zA
added newsitems, added some admin options to clear various caches.
2010-04-27 13:29:08 +00:00
# These lines were loaded from '/home/rbvermaa/src/hydra/src/lib/Hydra/Schema/Users.pm' found in @INC.
# They are now part of the custom portion of this file
# for you to hand-edit. If you do not either delete
# this section or remove that file from @INC, this section
# will be repeated redundantly when you re-create this
# file again via Loader! See skip_load_external to disable
# this feature.
1;
Reference in New Issue Copy Permalink