Can you e-mail me off the list with a schema dump of the database? I don't
want the content, just the schema.

I'd also like the result of:

    rb-site manage /path/to/site dumpdata -- --indent=2 django_evolution >
django_evolution_dump.json

And a screenshot of the two Django Evolution content listings (Evolutions
and Versions) in the Admin UI -> Database

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


On Wed, Sep 14, 2011 at 11:10 PM, Rohini Kumar Tharigonda
<rok...@gmail.com>wrote:

> [root@localhost rohini]# rb-site manage /var/www/reviewboard/ evolve
> -- --hint
> #----- Evolution for accounts
> from django_evolution.mutations import *
> from django.db import models
>
> MUTATIONS = [
>    AddField('Profile', 'is_private', models.BooleanField,
> initial=False)
> ]
> #----------------------
> #----- Evolution for reviews
> from django_evolution.mutations import *
> from django.db import models
>
> MUTATIONS = [
>    AddField('Comment', 'issue_opened', models.BooleanField,
> initial=False),
>    AddField('Comment', 'issue_status', models.CharField,
> max_length=1, null=True, db_index=True),
>    AddField('Group', 'local_site', models.ForeignKey, null=True,
> related_model='site.LocalSite'),
>    AddField('Group', 'incoming_request_count', models.CounterField,
> null=True),
>    AddField('Group', 'visible', models.BooleanField, initial=True),
>    AddField('Group', 'invite_only', models.BooleanField,
> initial=False),
>    ChangeField('Group', 'name', initial=None, unique=False),
>    AddField('Review', 'file_attachment_comments',
> models.ManyToManyField,
> related_model='reviews.FileAttachmentComment'),
>    AddField('ReviewRequestDraft', 'inactive_file_attachments',
> models.ManyToManyField, related_model='attachments.FileAttachment'),
>    AddField('ReviewRequestDraft', 'file_attachments',
> models.ManyToManyField, related_model='attachments.FileAttachment'),
>    AddField('ReviewRequest', 'inactive_file_attachments',
> models.ManyToManyField, related_model='attachments.FileAttachment'),
>    AddField('ReviewRequest', 'local_site', models.ForeignKey,
> null=True, related_model='site.LocalSite'),
>    AddField('ReviewRequest', 'local_id', models.IntegerField,
> null=True),
>    AddField('ReviewRequest', 'file_attachments',
> models.ManyToManyField, related_model='attachments.FileAttachment'),
>    AddField('DefaultReviewer', 'local_site', models.ForeignKey,
> null=True, related_model='site.LocalSite'),
>    AddField('ScreenshotComment', 'issue_opened', models.BooleanField,
> initial=False),
>    AddField('ScreenshotComment', 'issue_status', models.CharField,
> max_length=1, null=True, db_index=True)
> ]
> #----------------------
> #----- Evolution for scmtools
> from django_evolution.mutations import *
> from django.db import models
>
> MUTATIONS = [
>    AddField('Repository', 'review_groups', models.ManyToManyField,
> related_model='reviews.Group'),
>    AddField('Repository', 'local_site', models.ForeignKey, null=True,
> related_model='site.LocalSite'),
>    AddField('Repository', 'public', models.BooleanField,
> initial=True),
>    AddField('Repository', 'users', models.ManyToManyField,
> related_model='auth.User'),
>    ChangeField('Repository', 'path', initial=None, unique=False),
>    ChangeField('Repository', 'name', initial=None, unique=False)
> ]
> #----------------------
> Trial evolution successful.
> Run './manage.py evolve --hint --execute' to apply evolution.
> [root@localhost rohini]#
>
> On Sep 14, 11:41 am, Christian Hammond <chip...@chipx86.com> wrote:
> > What error? The one you pasted here?
> >
> > Going back to 1.6 won't solve anything. Your database is in an
> inconsistent
> > state now. Please run:
> >
> >     rb-site manage /path/to/site evolve -- --hint
> >
> > And paste the output.
> >
> > Christian
> >
> > --
> > Christian Hammond - chip...@chipx86.com
> > Review Board -http://www.reviewboard.org
> > VMware, Inc. -http://www.vmware.com
> >
> > On Tue, Sep 13, 2011 at 8:54 PM, Rohini Kumar Tharigonda
> > <rok...@gmail.com>wrote:
> >
> > > I tried upgrading it to 1.5.6 to 1.6.
> > > It gave error. Then came 1.6.1 immediately.
> > > How can upgrade RB to 1.6 instead of 1.6.1
> >
> > > On Sep 14, 5:48 am, Christian Hammond <chip...@chipx86.com> wrote:
> > > > At one point or another, you installed 1.6, not 1.6.1, but I'm
> guessing
> > > > something went wrong. Basically, your database already has the
> columns
> > > that
> > > > 1.6.1 thinks needs to be installed, but due to whatever happened,
> RB's
> > > > settings in your database didn't have that knowledge recorded.
> >
> > > > If I know what you attempted before, it'll help me to figure out the
> > > > solution.
> >
> > > > Christian
> >
> > > > --
> > > > Christian Hammond - chip...@chipx86.com
> > > > Review Board -http://www.reviewboard.org
> > > > VMware, Inc. -http://www.vmware.com
> >
> > > > On Tue, Sep 13, 2011 at 2:40 AM, Rohini Kumar Tharigonda
> > > > <rok...@gmail.com>wrote:
> >
> > > > > I have installed review board with yum
> > > > > (ReviewBoard-1.5.6-1.fc15.noarch)
> >
> > > > > I did the following . I get error while upgrading  site.
> >
> > > > > root@localhost conf.d]# easy_install -U ReviewBoard
> >
> > > > > install_dir /usr/lib/python2.7/site-packages/
> > > > > Searching for ReviewBoard
> > > > > Readinghttp://pypi.python.org/simple/ReviewBoard/
> > > > > Readinghttp://www.reviewboard.org/
> > > > > Readinghttp://downloads.reviewboard.org/releases/ReviewBoard/1.6/
> > > > > Readinghttp://downloads.reviewboard.org/releases/ReviewBoard/1.5/
> > > > > Readinghttp://downloads.reviewboard.org/releases/ReviewBoard/1.0/
> > > > > Readinghttp://www.review-board.org/
> > > > > Readinghttp://downloads.review-board.org/releases/
> > > > > Readinghttp://downloads.review-board.org/releases/ReviewBoard/1.0/
> > > > > Best match: ReviewBoard 1.6.1
> > > > > Downloading
> > > > >
> http://downloads.reviewboard.org/releases/ReviewBoard/1.6/ReviewBoard.
> > > ..
> > > > > Processing ReviewBoard-1.6.1-py2.7.egg
> > > > > creating
> /usr/lib/python2.7/site-packages/ReviewBoard-1.6.1-py2.7.egg
> > > > > Extracting ReviewBoard-1.6.1-py2.7.egg to /usr/lib/python2.7/site-
> > > > > packages
> > > > > Adding ReviewBoard 1.6.1 to easy-install.pth file
> > > > > Installing rb-site script to /usr/bin
> > > > > Installing rbssh script to /usr/bin
> >
> > > > > Installed
> /usr/lib/python2.7/site-packages/ReviewBoard-1.6.1-py2.7.egg
> > > > > Readinghttp://downloads.reviewboard.org/mirror/
> > > > > Processing dependencies for ReviewBoard
> > > > > Finished processing dependencies for ReviewBoard
> >
> > > > > [root@localhost conf.d]# rb-site upgrade /var/www/reviewboard/
> >
> > > > > Rebuilding directory structure
> > > > > Upgrading site settings_local.py
> > > > > Updating database. This may take a while.
> > > > > /usr/lib/python2.7/site-packages/Django-1.3.1-py2.7.egg/django/db/
> > > > > __init__.py:19: DeprecationWarning: settings.DATABASE_* is
> deprecated;
> > > > > use settings.DATABASES instead.
> > > > >  DeprecationWarning
> > > > > /usr/lib/python2.7/site-packages/Django-1.3.1-py2.7.egg/django/db/
> > > > > __init__.py:60: DeprecationWarning: Short names for ENGINE in
> database
> > > > > configurations are deprecated. Prepend default.ENGINE with
> > > > > 'django.db.backends.'
> > > > >  DeprecationWarning
> > > > > Creating tables ...
> > > > > Upgrading Review Board from 1.6 to 1.6.1
> > > > > There are unapplied evolutions for accounts.
> > > > > There are unapplied evolutions for reviews.
> > > > > There are unapplied evolutions for scmtools.
> > > > > Project signature has changed - an evolution is required
> > > > > Installing custom SQL ...
> > > > > Installing indexes ...
> > > > > No fixtures found.
> > > > > Error: Error applying evolution: (1060, "Duplicate column name
> > > > > 'is_private'")
> > > > > [root@localhost conf.d]#
> >
> > > > > --
> > > > > Want to help the Review Board project? Donate today at
> > > > >http://www.reviewboard.org/donate/
> > > > > Happy user? Let us know athttp://www.reviewboard.org/users/
> > > > > -~----------~----~----~----~------~----~------~--~---
> > > > > To unsubscribe from this group, send email to
> > > > > reviewboard+unsubscr...@googlegroups.com
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/reviewboard?hl=en
> >
> > > --
> > > Want to help the Review Board project? Donate today at
> > >http://www.reviewboard.org/donate/
> > > Happy user? Let us know athttp://www.reviewboard.org/users/
> > > -~----------~----~----~----~------~----~------~--~---
> > > To unsubscribe from this group, send email to
> > > reviewboard+unsubscr...@googlegroups.com
> > > For more options, visit this group at
> > >http://groups.google.com/group/reviewboard?hl=en
>
> --
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/donate/
> Happy user? Let us know at http://www.reviewboard.org/users/
> -~----------~----~----~----~------~----~------~--~---
> To unsubscribe from this group, send email to
> reviewboard+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/reviewboard?hl=en
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to