Thanks Christian :)
The corporate wiki upgrade instructions for reviewboard said that the syncdb
step was unnecessary for our set-up, and I believed it. I'm going to correct
the documentation (unfortunate that I had to reverse-engineer the truth of
the necessity, but there's no bug here but
Don't believe everything you read on the intranet :)
Glad it's working though! Let me know if there's anything else I can do.
Christian
On Tuesday, September 20, 2011, Josh stem...@gmail.com wrote:
Thanks Christian :)
The corporate wiki upgrade instructions for reviewboard said that the
Turns out if you read the directions life is a lot easier. I was missing the
'syncdb' step of successfully using Django Evolution. Crisis averted, yay...
I'm glad no one else had to spend time helping me discover this. ;)
On Fri, Sep 16, 2011 at 5:14 PM, stemcel stem...@gmail.com wrote:
Hey
Ugh, I wrote you an e-mail about this (on my iPhone) when I saw the post,
but I just realized it never sent. I have a draft saying to use syncdb :(
Glad you figured it out though.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. -
Hey reviewboard@,
When I try 'reviewboard/manage.py evolve --sql' I get the following
error output:
-- Evolve application sessions
CREATE INDEX `django_session_3da3d3d8` ON `django_session`
(`expire_date`);
-- Evolve application accounts
ALTER TABLE `accounts_profile` ADD COLUMN `is_private`
