Turns out if you read the directions life is a lot easier. I was missing the
'syncdb' step of successfully using Django Evolution. Crisis averted, yay...
I'm glad no one else had to spend time helping me discover this. ;)

On Fri, Sep 16, 2011 at 5:14 PM, stemcel <stem...@gmail.com> wrote:

> Hey reviewboard@,
> When I try 'reviewboard/manage.py evolve --sql' I get the following
> error output:
> -- Evolve application sessions
> CREATE INDEX `django_session_3da3d3d8` ON `django_session`
> (`expire_date`);
> -- Evolve application accounts
> ALTER TABLE `accounts_profile` ADD COLUMN `is_private` bool  DEFAULT
> False;
> ALTER TABLE `accounts_profile` ALTER COLUMN `is_private` DROP DEFAULT;
> ALTER TABLE `accounts_profile` MODIFY COLUMN `is_private` bool NOT
> -- Evolve application changedescs
>        ALTER TABLE changedescs_changedescription
>             MODIFY fields_changed LONGTEXT;
> Traceback (most recent call last):
>  File "./manage.py", line 154, in <module>
>    execute_manager(settings)
>  File "django/core/management/__init__.py", line 438, in
> execute_manager
>    utility.execute()
>  File "django/core/management/__init__.py", line 379, in execute
>    self.fetch_command(subcommand).run_from_argv(self.argv)
>  File "django/core/management/base.py", line 191, in run_from_argv
>    self.execute(*args, **options.__dict__)
>  File "django/core/management/base.py", line 220, in execute
>    output = self.handle(*args, **options)
>  File "django_evolution/management/commands/evolve.py", line 60, in
> handle
>    self.evolve(*app_labels, **options)
>  File "django_evolution/management/commands/evolve.py", line 140, in
> evolve
>    database))
>  File "django_evolution/mutations.py", line 418, in mutate
>    return self.add_column(app_label, proj_sig, database)
>  File "django_evolution/mutations.py", line 426, in add_column
>    self.field_attrs, model)
>  File "django_evolution/mutations.py", line 33, in create_field
>    related_model_sig = proj_sig[related_app_name][related_model_name]
> KeyError: 'site'
> The output of 'evolve --hint' is here: https://pastee.org/9gy2f
> My database schema dump is here: https://pastee.org/msrkq
> mysql> select * from django_evolution; here: https://pastee.org/urstg
> dumpdata --indent=2 django_evolution: https://pastee.org/szzg4
> I'm using DjangoEvolution 0.6.5 (r212) and Djblets 0.6.11. I've even
> gone as far as running the evolution under a debugger to try to figure
> out what the heck is going on, but I haven't had much luck with that
> so far.
> Can anyone please help? I've spent a great deal of time on this
> already and will continue working until I finish it, but I'm hoping
> someone on the list can contribute some insight into all this. I've
> already searched this list and the internet at large for similar
> issues, and have attached as much information as I can. Any hints
> would be appreciated!
> -josh

Want to help the Review Board project? Donate today at 
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to