selecting app for syncdb

328 views
Skip to first unread message

Michał Nowotka

unread,
May 22, 2013, 3:50:59 PM5/22/13
to django-d...@googlegroups.com
Hello,

Is the any particular reason why syncdb doesn't have argument with list of applications to be synced?

Aaron C. de Bruyn

unread,
May 22, 2013, 4:36:07 PM5/22/13
to django-d...@googlegroups.com
If you have south installed, I believe you can use migrate which takes an app argument.

python manage.py migrate myapp

-A


On Wed, May 22, 2013 at 12:50 PM, Michał Nowotka <mmm...@gmail.com> 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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Michał Nowotka

unread,
May 22, 2013, 5:15:50 PM5/22/13
to django-d...@googlegroups.com
I don't and I won't (south is not working with Oracle).

Shai Berger

unread,
May 22, 2013, 6:52:36 PM5/22/13
to django-d...@googlegroups.com
On Thursday 23 May 2013, Michał Nowotka wrote:
> I don't and I won't (south is not working with Oracle).

This discussion is getting to a place where it belongs either on django-users
or south-users; I should point out, though, that South does work with Oracle.
If I'm not mistaken, there are some problems with the latest released version
(0.7.6), which are already solved in the development version, and there is of
course the Oracle limitation of no-transactional-DDL; we picked an unreleased
version, and we use it in production with no special issues, in a project with
hundreds of migrations.

Shai.

Łukasz Langa

unread,
May 22, 2013, 6:57:28 PM5/22/13
to django-d...@googlegroups.com
On 23 maj 2013, at 00:52, Shai Berger <sh...@platonix.com> wrote:

If I'm not mistaken, there are some problems with the latest released version
(0.7.6)

FWIW, the latest released version is 0.8 as of earlier today:


-- 
Best regards,
Łukasz Langa

WWW: http://lukasz.langa.pl/
Twitter: @llanga
IRC: ambv on #python-dev

Shai Berger

unread,
May 22, 2013, 7:57:20 PM5/22/13
to django-d...@googlegroups.com
On Thursday 23 May 2013, Łukasz Langa wrote:
> On 23 maj 2013, at 00:52, Shai Berger <sh...@platonix.com> wrote:
> > If I'm not mistaken, there are some problems with the latest released
> > version (0.7.6)
>
> FWIW, the latest released version is 0.8 as of earlier today:
>
Can't take your eyes off Andrew for a minute... :)

Russell Keith-Magee

unread,
May 22, 2013, 9:54:30 PM5/22/13
to django-d...@googlegroups.com
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 <mmm...@gmail.com> wrote:
Hello,

Is the any particular reason why syncdb doesn't have argument with list of applications to be synced?

--
Reply all
Reply to author
Forward
0 new messages