📗
UpGrade Platform - Documentation
6.0
6.0
  • UpGrade Overview
  • Creating an Experiment
    • Unit of Assignment
    • Simple Experiment
    • Factorial Experiment
    • Inclusion and Exclusion
    • Schedule and Post-Rule
    • Exporting Experiment Data and Design
  • Creating a Feature Flag
  • How UpGrade Works
  • Researcher Guide
  • Developer Guide
    • ⚡Quick Start: Running UpGrade Locally with Docker
    • ⚡Quick Start: Running locally w/o Docker
    • UpGrade + AdapComp (Mooclet) in Docker
    • 🚶‍♀️Walkthroughs
      • Your Application and UpGrade
      • Example 1: A Quiz Web App
      • Example 2: An Online Math Game
    • 📚Reference
      • API
      • Client Libraries
        • TypeScript / JS
          • Class: UpgradeClient
          • Class: Assignment
          • SDK Interfaces
            • Interface: IMetric
            • Interface: IExperimentUser
            • Interface: IExperimentUserAliases
            • Interface: ILog
            • Interface: IMarkExperimentPoint
            • Interface: IMetric
            • Interface: IRequestOptions
            • Interface: IResponse
            • Interface: IUser
            • Interface: IUserGroup
      • Environment Variables
        • Frontend Environment
        • Backend Environment
      • Context Metadata
      • Metrics
      • Setting up Google-Auth
      • API Authorization
      • Data Architecture
    • 👨‍💻Contributing Code
      • Branching Workflow (Git-Flow)
      • Pull Request Expectations
    • 😅Troubleshooting
      • Relation ‘experiment_condition’ already exists
      • User not found. Authorization error
      • Token is not present in the request header
      • nodemon exits without explanation
      • Unable to find New Relic module configuration
      • No email received for export data
      • Opening a new tab in UpGrade prompts for re-authorization
      • Error: Cannot find module 'upgrade_types' (or a type from 'upgrade_types' does not exist)
  • Glossary
Powered by GitBook
On this page
  • Problem
  • Solution(s)
  1. Developer Guide
  2. Troubleshooting

Relation ‘experiment_condition’ already exists

PreviousTroubleshootingNextUser not found. Authorization error

Problem

Backend won't start due to: Relation ‘experiment_condition’ already exists

Solution(s)

Your Postgres server needs to be deleted and a new one is to be created. If you still have an issue then check the database on datagrip and if you still see tables present, drop the public schema tables and the object types and sequences folders in public.

OR

Set TYPEORM_SYNCHRONIZE variable of .env file to true while in the main branch and then start backend server, so you have the current base schema populated with you, then close the server. Now, switch to your branch that has schema changes and starts the server, and set TYPEORM_SYNCHRONIZE variable of .env file to false and run migration script to get the migration file generated.

😅