or maybe the the steps are out of
sequence. Please advise? thanks
Jasper
On Monday, January 18, 2016 at 2:19:31 PM UTC-5, Jasper Chow wrote:
>
> Thanks for the detailed explanation Christian . I have a clear picture
> now. really appreciated.
>
> Don't think it is a good
have the exact
> right schema now, and that data was sanely migrated. You'd have to examine
> the difference between your database schema and that of a new system, and
> examine all the evolution files that were applied, hand-applying any
> missing changes carefully to your database. D
e should be stored, so you may want to figure out whether
> you want to migrate that and update whatever it is that was using these
> fields.
>
> Christian
>
> --
> Christian Hammond - chri...@beanbaginc.com
> Review Board - https://www.reviewboard.org
> Beanbag, Inc.
then manual manipulation of database
schema is not recommended.
On Wednesday, January 13, 2016 at 1:06:43 PM UTC-5, Jasper Chow wrote:
>
>
> Attach evolve log ( rb-site manage /var/www/reviewboard evolve -- --hint
> ) for diagnosis
>
> thanks
>
>
> On Tuesday, J
Attach evolve log ( rb-site manage /var/www/reviewboard evolve -- --hint )
for diagnosis
thanks
On Tuesday, January 12, 2016 at 12:58:01 PM UTC-5, Jasper Chow wrote:
>
> Hello
>
> I am having issue similar to previous reported, while running rb-site
> upgrade
>
> htt
Hello
I am having issue similar to previous reported, while running rb-site
upgrade
https://hellosplat.com/s/beanbag/tickets/3967/
https://www.mail-archive.com/reviewboard@googlegroups.com/msg15947.html
information:
on Linux (CentOS) reviewboard 1.7 -> 2.0.16 ( intended to upgrade to latest
Hi Kevin
Can you please elaborate on the djanogo_evolution and how you rolled back ?
thanks
On Friday, December 11, 2015 at 4:43:26 AM UTC-5, Kevin Yin wrote:
>
> Turned out I have django_evolution version updated somehow. Rolling back
> to the previous version worked.
>
> On Tuesday,
