Changes between Initial Version and Version 1 of Ticket #21906, comment 2


Ignore:
Timestamp:
Feb 6, 2014, 2:41:21 PM (11 years ago)
Author:
yscumc

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #21906, comment 2

    initial v1  
    11After doing more digging, it seems that `allow_syncdb` is meant to define which models are are available on which particular database, and not just to prevent syncdb from acting upon a particular database.
    22
    3 I guess there should be change in logic and I believe the best resolution is to rename `allow_syncdb` or document this in the doc just like how the historic naming for `use_for_related_fields` is explained in https://docs.djangoproject.com/en/1.5/topics/db/managers/#writing-correct-managers-for-use-in-automatic-manager-instances
     3I guess there should be no change in the logic and I believe the best resolution is to rename `allow_syncdb` or document this in the doc just like how the historic naming for `use_for_related_fields` is explained in https://docs.djangoproject.com/en/1.5/topics/db/managers/#writing-correct-managers-for-use-in-automatic-manager-instances
Back to Top