Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
ensembl
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
1
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-gh-mirror
ensembl
Commits
e61f0169
Commit
e61f0169
authored
13 years ago
by
epaule
Browse files
Options
Downloads
Patches
Plain Diff
that readme is actually for the unmapped_reason table and *not* external_db
parent
eb827e26
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
misc-scripts/unmapped_reason/README-production_db.txt
+3
-3
3 additions, 3 deletions
misc-scripts/unmapped_reason/README-production_db.txt
with
3 additions
and
3 deletions
misc-scripts/unmapped_reason/README-production_db.txt
+
3
−
3
View file @
e61f0169
...
...
@@ -4,9 +4,9 @@ database.
The production database is kept on the ens-staging1 server and is called
"ensembl_production".
The master table for the
external_db
table is called
"master_unmapped_reason" and should be copied
as-is
to any new Core or
Core-like database.
The master table for the
unmapped_reason
table is called
"master_unmapped_reason" and should be copied to any new Core or
Core-like database
into the unmapped_reason table (as in: rename it)
.
For new entries, please insert them into this master table (after
notifying the current release coordinator).
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment