Glad to hear :) Thanks for reporting back on that.
We have some further improvements we're hoping to make for large diffsets
that should improve speed there too. Not sure when we're getting to that
(I'm juggling two large changes right now), but hopefully before too long.
Christian
--
Christian
The plan to dump my SQL, do a fresh install, and then insert the old
data worked just fine with a couple tweaks of the db data. I had a
large reviewboard DB and the new install has been working fine for a
week now.
I'd like to say that I absolutely had Django 1.0 and tip of Django
Evolution and t
The "unique" issue should have been fixed long ago, provided you have a
modern Django Evolution. Are you definitely running the latest SVN release,
and you don't have something really old installed somewhere?
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Tue, Oct 28, 2008
That is pretty much exactly what I did last week... Dumped my mysql
database without the table definitions, created a clean database,
loaded it with './manage.py syncdb', and then loaded my old data into
that database (after massaging a few things, like deleting the
permissions table and a few oth
After experimenting, I believe I can work around the db evolution bugs
by installing a fresh install of reviewboard, creating a new database,
and then bascially inserting my old database into a new db.
This has required a few tweaks to the old data, but otherwise
everything appears to be working
Here are some more details on this error in case someone can help...
When I run "./manage.py evolve --sql --hint" I see that the bad SQL
its trying to run is:
-- Evolve application scmtools
DROP INDEX id ON `scmtools_tool`;
If I try to run this command directly on reviewboard database (M
I've installed the official Django 1.0 Release and am having the same
problem. The ChangeField mutations just aren't working.
For example,
This Mutations:
ChangeField('Tool', 'id', initial=None, unique=False)
Appears to give this error:
The following are the changes that cou
I have the Django SVN version but at revision level -r8960 which was
at their 1.0 release time. Is that not sufficient? I don't see why i'd
need the official release if I have the SVN version at that revision
level. i'll give it a try none the less... sigh.
On Oct 3, 4:00 pm, "Christian Hammond"
According to our buildbot, it is working properly with the latest Django
Evolution.
I guess the other thing to check is that you are in fact running Django 1.0
and not somehow using the SVN release.
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Fri, Oct 3, 2008 at 3:40 PM
I'm definitely hitting the latest django-evolution. I've verified this
by running the manage.py script with python -v and verifing the import
path and also I have experimented to get various revisions of django-
evolution. Nothing works.
Has anyone confirmed evolution of ReviewBoard database work
Make sure you don't have a stale system-installed version in your python
path. I'll look into it to make sure it didn't break again, though at first
glance it doesn't appear to be.
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Fri, Oct 3, 2008 at 10:16 AM, mary <[EMAIL PRO
Hi,
In attempting to upgrade our ReviewBoard server to the latest and
greatest I'm running into errors running db evolutions 'Property
'unique' has changed'. (see errors below)
In previous posts it suggests this problem has been fixed however, I
have updated Django to revision (#8960 = r1.0), Dj
12 matches
Mail list logo
