Start to handle information about Git branches

Add some new pages /branches and /branch/... as well as a new git_branches
table. Also extend the email processing to enter the branch information in to
the database.
This commit is contained in:
Christopher Baines 2019-05-05 20:06:28 +01:00
parent ce4c3c6ed3
commit 5028dfe706
11 changed files with 382 additions and 19 deletions

View file

@ -0,0 +1,13 @@
-- Deploy guix-data-service:git_branches to pg
BEGIN;
CREATE TABLE git_branches (
name character varying NOT NULL,
commit character varying,
git_repository_id integer NOT NULL,
datetime timestamp without time zone NOT NULL,
CONSTRAINT name_commit PRIMARY KEY(name, commit)
);
COMMIT;

View file

@ -0,0 +1,7 @@
-- Revert guix-data-service:git_branches from pg
BEGIN;
DROP TABLE git_branches;
COMMIT;

View file

@ -6,3 +6,4 @@ appschema 2019-04-13T11:43:59Z Christopher Baines <mail@cbaines.net> # Add schem
buildstatus_enum [appschema] 2019-04-13T11:56:37Z Christopher Baines <mail@cbaines.net> # Creates the buildstatus enum
initial_import 2019-04-13T13:06:28Z Christopher Baines <mail@cbaines.net> # Import the manually managed database schema
git_repositories 2019-05-04T19:03:38Z Christopher Baines <mail@cbaines.net> # Add a git_repositories table
git_branches 2019-05-05T14:53:12Z Christopher Baines <mail@cbaines.net> # Add a git_branches table

View file

@ -0,0 +1,8 @@
-- Verify guix-data-service:git_branches on pg
BEGIN;
SELECT name, commit, git_repository_id, datetime
FROM git_branches WHERE FALSE;
ROLLBACK;