Skip to content

[Alembic] Creates migrations of tables that's migrations already exist #5301

@FoketzoRAI

Description

@FoketzoRAI

Describe the bug
After updating from 0.7.5 to 0.7.11, when I launch my reflex app, for some reason it notifies me that I have some changes (I don't have) and I have to make migrations.

I tried to understand what's happening:

  1. I see that on reflex 0.7.5 ... 0.7.10 here gives me False (which is OK) (if I'm not installing from 0.7.11)
Screenshots (OK & Downgrade from 0.7.11 to 0.7.9 and 0.7.8):

Image

Image

  1. But in 0.7.11 (and if I downgrade till 0.7.9) it gives me True with a migration with all my models in it.
Screenshots:

Image

Image

Image

To Reproduce
Steps to reproduce the behavior:

  • You should have some migrations on old reflex 0.7.5
  • Update to 0.7.11
  • Launch app and see message about making migrations.

Expected behavior
As I have existing migrations it shouldn't notify me about changes.

Specifics (please complete the following information):

  • Python Version: 0.13.2
  • Reflex Version: 0.7.11 (and if downgrade from it till 0.7.9)
  • OS: Ubuntu 24.04
  • Browser (Optional): -

Additional context

Created migration by checker (kinda change) is my all DB models in one migration.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions