Re: Evolution problem when upgrading from 1.6beta1 to 1.6beta2.1

2011-05-26 Thread kylebhamilton
Update - I believe I have fixed the problem. I tried to delete the django_evolution entries corresponding to the errors that I saw when trying to upgrade my site. However, some of those entries had added fields to the database so when I ran upgrade again, I received errors about duplicates. To s

Re: Evolution problem when upgrading from 1.6beta1 to 1.6beta2.1

2011-05-24 Thread kylebhamilton
Thanks for your response, Christian. I have never run "evolve --hint --execute". Until this last upgrade, I didn't know it existed and I only ran it with the --hint flag. It's good to know that I should never use that. I definitely will not in the future. We are using ReviewBoard at my work, s

Re: Evolution problem when upgrading from 1.6beta1 to 1.6beta2.1

2011-05-23 Thread Christian Hammond
Running evolve --hint --execute is the best way to cause breakages like this. You should never have a reason to run it, regardless of what people say on the forum or other sites, unless you're in some very specific development cases. What I imagine happened was that, for some reason, you ended up

Re: Evolution problem when upgrading from 1.6beta1 to 1.6beta2.1

2011-05-23 Thread kylebhamilton
I did upgrade with easy_install. I ran evolve --hint after getting this error and reading some forum posts on similar problems, but I haven't modified/cleared anything in the database. Thanks, Kyle On May 18, 2:38 pm, Christian Hammond wrote: > Sorry, you said the source version in the subject.

Re: Evolution problem when upgrading from 1.6beta1 to 1.6beta2.1

2011-05-23 Thread kylebhamilton
I ran evolve --hint after reading some of the forum posts on error such as this, but I didn't try to make the database changes. I haven't modified or cleared the database. Kyle On May 18, 2:38 pm, Christian Hammond wrote: > Sorry, you said the source version in the subject. > > Most of those fi

Re: Evolution problem when upgrading from 1.6beta1 to 1.6beta2.1

2011-05-18 Thread Christian Hammond
Sorry, you said the source version in the subject. Most of those fields were present in beta 1. At any point, did you ever run evolve --hint, or in any way modify your database (even clear it)? Christian On Wednesday, May 18, 2011, Christian Hammond wrote: > Hey Kyle, > > What version are you c

Re: Evolution problem when upgrading from 1.6beta1 to 1.6beta2.1

2011-05-18 Thread Christian Hammond
Hey Kyle, What version are you coming from? These are all things that have evolution files, so it sounds like they may not be processed correctly. I assume you upgraded with easy_install? Christian On Wednesday, May 18, 2011, kylebhamilton wrote: > I just installed the new beta 2.1 and tried t