On Tue, Apr 2, 2013 at 4:57 PM, Serdar Dalgic <[email protected]> wrote:
> On Tue, Apr 2, 2013 at 11:48 PM, Bill Freeman <[email protected]> wrote: > > Perhaps take the site down (or clone it), set managed = True, ask > manage.py > > for sql for that app, and put everything back? > > > > Sure, that's a way to do it. But I'm looking for a practical way to do > it. Otherwise, commenting out the managed=True lines in the models.py > is an option too :) > > -- > - Serdar Dalgıç <[email protected]> > FLOSS Developer, Life & Nature Hacker > > -- > You received this message because you are subscribed to the Google Groups > "Django users" 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-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > Yes. I must confess that I like your solution better. But some folks are loth to edit the stuff that isn't their code. Maybe create a patch adding a command line flag that says you want the unmanaged moddels as well, and offer it to the core team? Them taking it, however, wouldn't help you with 1.3.2. -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
