Skip to content
This repository has been archived by the owner on Jan 31, 2020. It is now read-only.

schema errors during Make are not caught #163

Open
gatoravi opened this issue Feb 24, 2015 · 1 comment
Open

schema errors during Make are not caught #163

gatoravi opened this issue Feb 24, 2015 · 1 comment
Assignees

Comments

@gatoravi
Copy link
Contributor

Errors like

DBD::Pg::st execute failed: ERROR: duplicate key value violates unique constraint "group_pkey"
DETAIL: Key (id)=(1) already exists. at /opt/gms/UMBIU92/sw/ur/lib/UR/DBI.pm line 888.
ERROR: Genome::DataSource::GMSchema: Error executing SQL:
INSERT INTO disk.group (unix_uid,unix_gid,subdirectory,permissions,name,id) VALUES (?,?,?,?,?,?)
PARAMS: '2001', '2001', 'info', '775', 'reads', '1'
ERROR: duplicate key value violates unique constraint "group_pkey"
DETAIL: Key (id)=(1) already exists.
ERROR: Failed to sync data source: Genome::DataSource::GMSchema: Genome::DataSource::GMSchema: Error executing SQL:
INSERT INTO disk.group (unix_uid,unix_gid,subdirectory,permissions,name,id) VALUES (?,?,?,?,?,?)
PARAMS: '2001', '2001', 'info', '775', 'reads', '1'
ERROR: duplicate key value violates unique constraint "group_pkey"
DETAIL: Key (id)=(1) already exists.

slip through the install process. We need to catch these errors.

@gatoravi gatoravi self-assigned this Feb 25, 2015
@gatoravi gatoravi added the bug label Feb 25, 2015
@gatoravi
Copy link
Contributor Author

this error might have been caused due to trying to insert same values into the table again(by re-running make) hence violating some primary-key constraints. It would still help to catch these and die during the make process.

@gatoravi gatoravi assigned sakoht and unassigned gatoravi Apr 4, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants