-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gfa path export #48
Gfa path export #48
Conversation
@@ -85,7 +85,7 @@ CREATE TABLE path_edges ( | |||
FOREIGN KEY(edge_id) REFERENCES edges(id), | |||
FOREIGN KEY(path_id) REFERENCES path(id) | |||
) STRICT; | |||
CREATE UNIQUE INDEX path_edges_uidx ON path_edges(path_id, edge_id); | |||
CREATE UNIQUE INDEX path_edges_uidx ON path_edges(path_id, edge_id, index_in_path); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This resolves the constraint violations that Bob saw
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same sequence (or pair of edges) can show up multiple times in a path with this
0dfb7fc
to
f6d5c34
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it looks good. Only comment is about a convention i've been trying to use for column table order in our generic query methods
No description provided.