Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete two_factor/migrations/0001_squashed_0008_delete_phonedevice.py #667

Closed
wants to merge 1 commit into from

Conversation

hyperkai
Copy link

@hyperkai hyperkai commented Sep 15, 2023

This file causes the error below so I deleted it:

django.db.utils.OperationalError: no such table: two_factor_phonedevice

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

This file causes the error below so I deleted it:

> django.db.utils.OperationalError: no such table: two_factor_phonedevice
@hyperkai
Copy link
Author

hyperkai commented Sep 15, 2023

I deleted two_factor/migrations/0001_squashed_0008_delete_phonedevice.py because the file causes the error below:

django.db.utils.OperationalError: no such table: two_factor_phonedevice

@hyperkai hyperkai closed this Sep 15, 2023
@hyperkai hyperkai reopened this Sep 15, 2023
@pacharanero
Copy link

pacharanero commented Sep 18, 2023

Not sure if this is directly related but we do also seem to have an issue with unapplied migrations having recently implemented two_factor in our app. We have a step in our Docker Compose file which runs python manage.py migrate but for some reason we don't understand this one migration is not being applied.

We get a warning in the log console "You have 1 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): two_factor." and when entering the relevant Docker container and running python manage.py migrate again, it then applies the migration: Applying two_factor.0001_squashed_0008_delete_phonedevice... OK but we don't see why this should be necessary when all our other migrations get applied automatically during the provisioning of the Docker Compose setup.

cc @eatyourpeas @anchit-chandran

@mlec1
Copy link
Contributor

mlec1 commented Sep 23, 2023

@hyperkai I would suggest opening an issue instead.

Which version of the package are you using ? The table you mention is not in the file you want to delete. It is in the phonenumber plugin

@moggers87
Copy link
Collaborator

Closing this as I think this is a duplicate of #647

@moggers87 moggers87 closed this Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants