Re: DB Evolution: Property unique has changed

2008-10-28 Thread plumpy
That is pretty much exactly what I did last week... Dumped my mysql database without the table definitions, created a clean database, loaded it with './manage.py syncdb', and then loaded my old data into that database (after massaging a few things, like deleting the permissions table and a few

Re: DB Evolution: Property unique has changed

2008-10-28 Thread Christian Hammond
The unique issue should have been fixed long ago, provided you have a modern Django Evolution. Are you definitely running the latest SVN release, and you don't have something really old installed somewhere? Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Tue, Oct 28, 2008

Re: DB Evolution: Property unique has changed

2008-10-24 Thread mary
Here are some more details on this error in case someone can help... When I run ./manage.py evolve --sql --hint I see that the bad SQL its trying to run is: -- Evolve application scmtools DROP INDEX id ON `scmtools_tool`; If I try to run this command directly on reviewboard database

Re: DB Evolution: Property unique has changed

2008-10-03 Thread mary
I'm definitely hitting the latest django-evolution. I've verified this by running the manage.py script with python -v and verifing the import path and also I have experimented to get various revisions of django- evolution. Nothing works. Has anyone confirmed evolution of ReviewBoard database

Re: DB Evolution: Property unique has changed

2008-10-03 Thread mary
I have the Django SVN version but at revision level -r8960 which was at their 1.0 release time. Is that not sufficient? I don't see why i'd need the official release if I have the SVN version at that revision level. i'll give it a try none the less... sigh. On Oct 3, 4:00 pm, Christian Hammond