-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[BUG] Migrating with another database other than "default" #7774
Comments
nzprog
changed the title
[BUG] Migrating with another database (clean of DjangoCMS tables)
[BUG] Migrating with another database other than "default"
Jan 21, 2024
@nzprog Would you like to create a PR? |
I've never done a pull request before, Are there steps for this for DjangoCMS? |
Hi @nzprog ! Quick Guide to Contributing to
|
@nzprog Do you want to give it a try? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I am creating another database with tables not used with DjangoCMS and found a bug in the migration code.
see file .venv/lib/python3.11/site-packages/cms/migrations/0030_auto_20180810_0629.py
On line 29:
Should include the alias for the current database
Steps to reproduce
./manage migrate --database=OTHER_DATABASE
Expected behaviour
The migration should succeed.
Actual behaviour
Screenshots
Additional information (CMS/Python/Django versions)
Django 5.0.1
django-cms 4.1.0
python 3.11
Do you want to help fix this issue?
Ummm, the fix is in the comment above, if someone could put that in, it would be nice.
I tried to join the community but as per my other post, https://www.django-cms.org/en/sign-up-work-contribution/ catchup isn't working.
The text was updated successfully, but these errors were encountered: