The SVG schema is very helpful! Attaching the SQL required to import this into PostgreSQL
Much better! Created merge_requests/1 If I get feedback from the researchers send it your way.
for reference, here are the table sizes of the imported database
uniparc=# \dt+
List of relations
Schema | Name | Type | Owner | Size | Description
--------+-----------------------+-------+---------+--------+-------------
public | chain | table | uniparc | 35 MB |
public | component | table | uniparc | 16 GB |
public | domain | table | uniparc | 182 GB |
public | gene_name | table | uniparc | 68 GB |
public | kb_accession | table | uniparc | 17 MB |
public | ncbi_gi | table | uniparc | 26 GB |
public | ncbi_taxonomy_id | table | uniparc | 35 GB |
public | protein_name | table | uniparc | 48 GB |
public | proteome_id | table | uniparc | 60 GB |
public | uniparc | table | uniparc | 141 GB |
public | xref | table | uniparc | 245 GB |
public | xref_chain | table | uniparc | 35 MB |
public | xref_component | table | uniparc | 55 GB |
public | xref_gene_name | table | uniparc | 169 GB |
public | xref_kb_accession | table | uniparc | 18 MB |
public | xref_ncbi_gi | table | uniparc | 23 GB |
public | xref_ncbi_taxonomy_id | table | uniparc | 173 GB |
public | xref_protein_name | table | uniparc | 115 GB |
public | xref_proteome_id | table | uniparc | 55 GB |
Honestly I'm not sure about the use case! I'm a system/database database administrator, and was asked to get the uniparc data into a database for a researcher.
I am confused about how to create a pull request. I can fork the project, push a new branch, but when I click on Merge Reqeusts -> New Merge Request I can't select the upstream project. Is this a feature that needs to be allowed/enabled on your repository?
The SVG schema is very helpful! Attaching the SQL required to import this into PostgreSQL