Hi Christian,
Thanks for the fast response. I haven't tried upgrading things. I guess I
could try that, but I got the impression from somewhere that it would be
difficult to do so from the early version that we are currently running. If
you think it is worth trying, then that is probably the ideal
ts, or was it using ./manage.py evolve?
>
> Also, were you using rb-site?
>
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Fri, Aug 20, 2010 at 9:05 PM,
want to
> just start off with a new install.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Sat, Aug 21, 2010 at 7:22 AM, Jon Stevens wrote:
> I'm
uests numbered up that high.
>
> (Of course, I changed reviews_reviewrequest *after* changing
> reviews_review. So now my IDs in the reviews_review table are
> starting at around 2. Gulp!)
>
> Thanks,
>
> m@
>
> On Aug 21, 6:48 pm, Jon Stevens wrote:
> &g
the thing you want to adjust reviews_reviewrequest table, so
> > > that the review *request* numbers don't collide with the old ones,
> > > rather than the completed review records? .
> >
> > > Once I executed ALTER TABLE reviews_reviewrequest 2; I got revie
Sure, as soon as google code is fixed. ;-) It's down for me... they've been
having a lot of stability issues recently. =(
jon
On Tue, Oct 26, 2010 at 2:22 PM, Christian Hammond wrote:
> I think there's likely a problem due to the diff indicating a change to an
> existing revision when really tha
