Hi Michael,
Absolutely.
For one-off database repairs, we charge $200 USD/hour for the repair. As I
mentioned, this usually takes no more than 2 hours, sometimes upwards of 3,
but we have a lot of experience at this point in correcting these issues
once we get our hands on things.
What we then
Thank you, Christian. Could you please send me some details about the fees
involved so that I can present to my management?
Mike
On Saturday, March 19, 2016 at 6:37:14 PM UTC-6, Christian Hammond wrote:
>
> Hi Michael,
>
> I've seen this error before, and it's always been due to a prior
Hi Michael,
I've seen this error before, and it's always been due to a prior upgrade in
some prior version being forced using 'evolve --hint --execute," which can
mess up the history and require manual repair. I'm not seeing anything in
the output indicating anything otherwise. Is it possible
Hi, Christian --
Is this output helpful in determining what to do next?
Thank you!
Mike
On Friday, March 11, 2016 at 12:21:17 PM UTC-7, Michael Lund wrote:
>
> The server is running Django 1.4.22
>
> Here is the requested output:
>
> >>> from django_evolution.models import Version
> >>> for v
The server is running Django 1.4.22
Here is the requested output:
>>> from django_evolution.models import Version
>>> for v in Version.objects.order_by('pk'):
...print '%s - %s - %s' % (v.pk, v.evolutions.count(), v.when)
...
1 - 7 - 2010-03-05 15:48:24+00:00
2 - 7 - 2011-03-06
Hi Michael,
Sounds like some state got messed up on your end, too.
Can you find the script I had Risha run (the one with the Version import)?
Any other info you can provide that we went through earlier on the thread
would also help.
Basically... That KeyError means you have state missing that
You can install any version of Reviewboard using easy_install. Look at the
documentation here:
https://www.reviewboard.org/docs/manual/2.0/admin/installation/development-releases/#installing-development-releases
For example to install Version 1.6:
easy_install -f
Is there a straightforward way to determine the location of the offending
key?
I wonder whether I can circumvent some issues by upgrading incrementally to
intermediate versions of ReviewBoard -- I'm taking a pretty big leap. I
have installed via easy_install, which has of course taken the
Thanks for the follow-up, Risha! I'm glad it's working :) Hopefully this
will help someone else down the road.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com
On Wed, Jul 29, 2015 at 4:21 PM, Risha
Can you run the following:
$ rb-site manage /path/to/site shell
from django_evolution.models import Version
for v in Version.objects.order_by('pk'):
print '%s - %s - %s' % (v.pk, v.evolutions.count(), v.when)
That'll give me a sense of what evolutions are applied. There's a
I'm not sure if it makes any difference but yesterday I ran the rb-site
manage evolve --hint and execute commands. I have attached the output of
both of those in the attached document. It didn't seem to make a
difference, rb-site upgrade still gives me the same issue.
rb-site_evolve
Hi Risha,
Hmm, I'm not seeing what I was expecting to see there.
It's possible that there's a bug in upgrading to 2.5, due to one of the
changes we've made. I'm going to be investigating this. For now, I'd
suggest taking a copy of the 1.6 database and upgrading to the latest 2.0.x
release
No, that doesn't help either.
# rb-site manage /var/ReviewBoard syncdb
Creating tables ...
There are unapplied evolutions for auth.
The following content types are stale and need to be deleted:
auth | message
Any objects related to these content types by a foreign key will also
be deleted.
Hi Risha,
That's strange. It's like some state is missing there.
Can you try doing this first:
$ rb-site manage /var/ReviewBoard syncdb
and then do the upgrade? See if that gets any further.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board -
14 matches
Mail list logo
