Skip to content

migrations do not work after cloning from scratch #256

Description

@bhemmer

when cloning the repository and running makemigrations, django need input for a lot of default values

Activity

  1. bhemmer commented on Nov 13, 2022

    @bhemmer
    MemberAuthor

    #02ae996 on branch migrations does the following:

    When cloning from scratch, running makemigrations asked me to specify a lot of defaults. With the new migrations this does not happen.
    With the updated migrations, running migrate from scratch and afterwards copying the previous development DB works. This would be helpful for new contributors.

    I am not sure how this will impact production though. @spuetz could you please review that?
    I have not much experience with migrations: Is doing this a bad idea?
    Should we do a PR for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions