On 8/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Oh. That's a real ouch. I really hoped I can avoid that.
Well, consider this:
Anything which *isn't* SQL and which is used to do this job must -- in
order to cover all the necessary use cases -- be as complex as SQL, or
evolve to the poi
It might be worth reading the wiki page on the Schema Evolution [1],
and if you're not using SVN, there is a patch [2] against Django 0.96
which implements schema evolution.
Other than that, you might want to look into dmigrate [3] (which I've
not personally used, so I'm not sure how mature it is
Oh. That's a real ouch. I really hoped I can avoid that.
Thanks anyhow.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To un
On 8/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> What I'd normally do is use alter table to update the fields. I was
> surprised to see django won't do it, while using manage.pl syncdb. Is
> there a practical way to handle this issue? Or am I doomed to live
> with the tables I've created
Hi. I'm about to start my own django project soon. I just wanted to
know how you handle table structure change? For instance, I have this
model from the tutorial:
class Poll(models.Model):
question = models.CharField(maxlength=200)
pub_date = models.DateTimeField('date published')
def
5 matches
Mail list logo
