Hi Michał, The short answer is "inter-application dependencies".
For example, if one application has a foreign key on a second application, and you only synchronise the first application, you won't be able to set up any foreign key constraints on the first application. If you use the project in this incomplete state, you'll get unpredictable behaviour from any join on this foreign key. Then, when you *do* run the syncdb on the second application, you need to be able to identify which foreign key columns have been correctly constrained. While it may be *possible* to resolve these issues, it's must easier to just synchronise everything. Is there a particular reason that you want a per-app syncdb? I'm having difficulty thinking of a use case where this would be beneficial. Yours, Russ Magee %-) On Thu, May 23, 2013 at 3:50 AM, Michał Nowotka <[email protected]> wrote: > Hello, > > Is the any particular reason why syncdb doesn't have argument with list of > applications to be synced? > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers?hl=en > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
