Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • ensembl
  • Merge requests
  • !459

Closed
Created Dec 17, 2019 by Marek Szuba@mks
  • Report abuse
Report abuse

Core db schema patch to support longer assembly names in the mapping_session table.

  • Overview 2
  • Commits 6
  • Changes 33

Created by: ens-carlos

Requirements

  • Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
  • Review the contributing guidelines for this repository; remember in particular:
    • do not modify code without testing for regression
    • provide simple unit tests to test the changes
    • if you change the schema you must patch the test databases as well, see Updating the schema
    • the PR must not fail unit testing

Description

Using one or more sentences, describe in detail the proposed changes. Increased length of old_assembly and new_assembly columns in the mapping_session table in the core databases.

Use case

Describe the problem. Please provide an example representing the motivation behind the need for having these changes in place. Xenopus tropicalis assembly name would appear truncated as "Xenopus_tropicalis_v" in the current database schema for e100.

Benefits

If applicable, describe the advantages the changes will have. Longer assembly names would be supported.

Possible Drawbacks

If applicable, describe any possible undesirable consequence of the changes. More space would be required.

Testing

Have you added/modified unit tests to test the changes? No. I think the existing unit tests should work. If so, do the tests pass/fail? N/A. Have you run the entire test suite and no regression was detected? No.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/ens-carlos/patch-3