[Feature Request] django-admin migrate - skip feature

[Fábio Molinar]

Hi,

I have a project with two apps (app1, app2). App1's DB is the default DB. 
App2's DB is DB2. To run the migrations on DB2, I need to run:

python manage.py migrate app2 --database=DB2

Which is ok. The problem is to run the migrations for the rest of the 
project. I would like to run all migrations with the exception of app2's 
migrations on the default DB. To do that, I need to run every single app 
migration separately, with the exception of app2's migration. It would be 
great if I could type something like this instead:

python manage.py migrate --skip=app2

And that command would run all other migrations on the default DB with the 
exception of app2's migrations. 

I posted a question on stackoverflow regarding this: 
https://stackoverflow.com/questions/53850114/migrate-command-create-all-tables-on-second-db-django

And I hope this is the correct mail-list to ask for a feature.

Regards,
Fabio

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/791a11e9-8848-4c96-a4b6-0c8bfcbf55cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Feature Request] django-admin migrate - skip feature

[Adam Johnson]

There's a new answer on your stack overflow post that I think answers your
question: https://stackoverflow.com/a/53870659/1427135 . The database
router can already do it :)

On Thu, 20 Dec 2018 at 07:23, Fábio Molinar  wrote:

> Hi,
>
> I have a project with two apps (app1, app2). App1's DB is the default DB.
> App2's DB is DB2. To run the migrations on DB2, I need to run:
>
> python manage.py migrate app2 --database=DB2
>
> Which is ok. The problem is to run the migrations for the rest of the
> project. I would like to run all migrations with the exception of app2's
> migrations on the default DB. To do that, I need to run every single app
> migration separately, with the exception of app2's migration. It would be
> great if I could type something like this instead:
>
> python manage.py migrate --skip=app2
>
> And that command would run all other migrations on the default DB with the
> exception of app2's migrations.
>
> I posted a question on stackoverflow regarding this:
> https://stackoverflow.com/questions/53850114/migrate-command-create-all-tables-on-second-db-django
>
> And I hope this is the correct mail-list to ask for a feature.
>
> Regards,
> Fabio
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/791a11e9-8848-4c96-a4b6-0c8bfcbf55cd%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM0KSRkypMZJx9FCC_U6v6dxr8s4HsGced%3DyEVu1cCjP3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Fellow Reports - December 2018

[Tim Graham]

Week ending December 8, 2018

Authored

--

https://github.com/django/django/pull/10726 - Fixed #30013 -- Fixed 
DatabaseOperations.last_executed_query() with mysqlclient 1.3.14+.

Reviewed/committed

--

https://github.com/django/django/pull/10731 - Fixed #30011 -- Fixed queries 
that reuse filtered aggregates.

https://github.com/django/django/pull/10718 - Fixed #29895 -- Doc'd why 
MySQL's atomic DDL statements don't work for atomic migrations.

https://github.com/django/django/pull/10657 - Fixed #28766 -- Added 
ResolverMatch.route.

https://github.com/django/django/pull/10733 - Fixed #29182 -- Fixed schema 
table alteration on SQLite 3.26+.
https://github.com/django/django/pull/10735 - Fixed #30023 -- Prevented 
SQLite schema alterations while foreign key checks are enabled.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1112a3b9-f9e2-400f-8bff-1faec09e265d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Reports - December 2018

[Tim Graham]

Week ending December 15, 2018

(vacation)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d2f1e176-3695-4d13-b086-2c26ed55b42f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.