Thanks for the advice. South installed, but glitches on converting
(that I'll no doubt iron out).
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group,
On Jun 6, 2010, at 9:18 AM, Andy Kelley wrote:
> Use south. The overhead is worth it.
+1 on South.
Especially because this "just this once" scenario is going to happen again and
again if your project lives long enough.
Shawn
--
You received this message because you are subscribed to the Goo
Use south. The overhead is worth it.
On Jun 5, 12:57 pm, Dave E wrote:
> ah. forgot about the plain text in Google Groups... apologies. Again,
> in English:
>
> Given that Syncdb won't ever issue an alter table command ('no such
> column'), that Schema Evolution is still in debate, that South is
ah. forgot about the plain text in Google Groups... apologies. Again,
in English:
Given that Syncdb won't ever issue an alter table command ('no such
column'), that Schema Evolution is still in debate, that South is a
bit of an overhead if all you want to do is add a field to an existing
model - o
Given that Syncdb won't ever issue an alter table command ('no such
column'), that http://code.djangoproject.com/wiki/
SchemaEvolution">Schema Evolution is still in debate, that http://south.aeracode.org/";>South is a bit of an overhead if
all you want to do is add a field to an existing model - on
5 matches
Mail list logo
