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

54 lines
875 B
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;
package Hydra::Schema::SchemaVersion;
# Created by DBIx::Class::Schema::Loader
# DO NOT MODIFY THE FIRST PART OF THIS FILE
=head1 NAME
Hydra::Schema::SchemaVersion
=cut
use strict;
use warnings;
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");
sql: Generate models from postgresql Lowercasing is due to postgresql not having case-sensitive table names. It always technically workde before, but those table names never existed literally. The switch to generating from postgresql is to handle an upcoming addition of an auto-incrementign ID to the Jobset table. Sqlite doesn't seem to be able to handle the table having an auto incrementing ID field which isn't the primary key, but we can't change the primary key trivially. Since hydra doesn't support sqlite and hasn't for many year anyway, it is easier to just generate from pgsql directly.
2020-02-06 12:23:47 -05:00
=head1 TABLE: C<schemaversion>
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
=cut
sql: Generate models from postgresql Lowercasing is due to postgresql not having case-sensitive table names. It always technically workde before, but those table names never existed literally. The switch to generating from postgresql is to handle an upcoming addition of an auto-incrementign ID to the Jobset table. Sqlite doesn't seem to be able to handle the table having an auto incrementing ID field which isn't the primary key, but we can't change the primary key trivially. Since hydra doesn't support sqlite and hasn't for many year anyway, it is easier to just generate from pgsql directly.
2020-02-06 12:23:47 -05:00
__PACKAGE__->table("schemaversion");
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 ACCESSORS
=head2 version
data_type: 'integer'
is_nullable: 0
=cut
Merge the BuildSchedulingInfo table into the Builds table This simplifies the code and improves performance since it reduces the number of joins.
2012-02-29 02:22:49 +01:00
__PACKAGE__->add_columns("version", { data_type => "integer", is_nullable => 0 });
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
sql: Generate models from postgresql Lowercasing is due to postgresql not having case-sensitive table names. It always technically workde before, but those table names never existed literally. The switch to generating from postgresql is to handle an upcoming addition of an auto-incrementign ID to the Jobset table. Sqlite doesn't seem to be able to handle the table having an auto incrementing ID field which isn't the primary key, but we can't change the primary key trivially. Since hydra doesn't support sqlite and hasn't for many year anyway, it is easier to just generate from pgsql directly.
2020-02-06 12:23:47 -05:00
# Created by DBIx::Class::Schema::Loader v0.07049 @ 2020-02-06 12:22:36
# DO NOT MODIFY THIS OR ANYTHING ABOVE! md5sum:2wy4FsRYVVo2RTCWXcmgvg
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
# You can replace this text with custom code or comments, and it will be preserved on regeneration
1;
Reference in New Issue Copy Permalink