Your plan to use ALTER TABLE should work. review_request_id just holds the
current ID. That's what should be auto_increment. I think so long as you do
that, you'll see the review request ID number you expect.
By the way, what problems did you hit with upgrading?
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Fri, Aug 20, 2010 at 5:47 PM, jon <latch...@gmail.com> wrote:
> Apologies if this has been covered before, google didn't seem to have
> an obvious answer. Is it possible to set a starting review # for a
> clean install?
> The issue is that we have a pre-1.0 installation that has been in use
> for awhile now. Instead of trying to figure out how to upgrade the
> database, I've just created a fresh new installation (of 1.5rc1) on a
> fresh new server and we are just going to consider the previous
> version effectively read-only.
> But, on the new server, I'd like to start the review number +1 higher
> than the old server so that we don't have conflicting numbers in svn
> commit messages.
> I see that reviews_review.id is auto_increment. I know that I can do:
> "ALTER TABLE reviews_review AUTO_INCREMENT = 100;", but I also see a
> 'review_request_id' column. What is that used for? Do you see any
> other issues with this approach?
> 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
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