Migration not working

[justin-ven]

Related to #124, a migration file now seems to be included in 5.0, but results (at least on my system) in the following error:

psycopg2.errors.ObjectNotInPrerequisiteState: sequence must have same owner as table it is linked to

[svandeneertwegh]

Agree, i have the same issue

[svandeneertwegh]

When i copie the git folder robots direct in my project and remove 0002 migration. Then run manage.py makemigrations robots, it returns "No changes detected in app 'robots'".

[tony]

This needs more information.

Not clear if this is a configuration issue on your side(s) or a django-robots issue.

psycopg2.errors.ObjectNotInPrerequisiteState: sequence must have same owner as table it is linked to

@svandeneertwegh @justin-ven It looks like you may need superuser access / to iron permissions out. Have you tried troubleshooting yet on the postgres side?

[justin-ven]

This issue is now resolved on my system - I just upgraded to Django 4.0.3, and let the migration set up and work through. I did need to merge two migrations on one system, but otherwise things seem to be functioning correctly for me now.

[tony]

Related to #124

I am about to release a beta release of 5.x that includes a missing app setting via #134 - in re #124.

[tony]

In re:

... results (at least on my system) in the following error:

psycopg2.errors.ObjectNotInPrerequisiteState: sequence must have same owner as table it is linked to

psycopg2.errors.ObjectNotInPrerequisiteState: sequence must have same owner as table it is linked to

I'm don't think this is something the package itself can solve - I'm open to being convinced otherwise.

These are highly specific to your own project's state, migrations are complicated.

Don't take my / other's word on these: it depends 100% on your specific circumstance!

• You may need to go in manually to django_migrations and see if a migration really ought to be run
  • It may be a case where makemigrations was ran to headoff the problem is Migrations are missing for 5.0 #124, in which case you could need to remove the offending row and ./manage.py migrate robots --fake.
  • There's a stackoverflow QA here: https://stackoverflow.com/q/70761679/1396928
• Check which version of django-robots you're using
  • 5.0 has a migration for BigAutoField but is missing a local app-related setting (fixed via Set default auto field to BigAutoField #134, build yet to be released, likely as 5.1beta0, 5.1beta, etc

I will close, but keep the issue unlocked so workarounds / solutions can be shared. I'm not sure if it's #124 or not.

I will also come back when a PyPI beta package with the #124 is live