Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.webbeat.web
  • Issues
  • #219

Closed
Open
Created Jul 16, 2015 by André Anjos@andre.anjos💬Owner

Natural keys fixture dumping for BEAT objects is missing

Since a long time we have the option to backup using natural primary and foreign keys, but this setting is not effective for our BEAT objects.

This triggered a bug while trying to do a restore on our new staging server: experiments reference database sets with integer foreigns keys, but there is no certainty that database sets will be re-stored on the same order or with the same primary keys, given they are re-created at restore time.

To fix this issue for good, we'd need to implement natural_key() and get_by_natural_key() on the relevant classes throughout the project.

Assignee
Assign to
Time tracking